3 ms·
This bothered me a lot: > I seem to have a knack for trying to write things in Rust that rely on intertangled references and mutability: first a game, then a U
by bsder 12y ago
This bothered me a lot:
> I seem to have a knack for trying to write things in Rust that rely on intertangled references and mutability: first a game, then a UI library…
First of all, a UI library is EXACTLY the kind of thing I want you running through Rust and having a long, drawn out fight over mutability. Every UI we currently have absolutely sucks in a multi-threaded context. I want the compiler to make you think long and hard that maybe, just maybe your ideas about how to architect a GUI library are very broken and that you have to restart from a clean slate.
As for a game, do you really have that much mutable state, or are you just conditioned to use mutable state by default? Games do have lots of mutable state, but games also have lots of bugs due to multi-threading that being forced to analyze mutable state exposes.