I kinda feel like complaints that using indexing over refs is "bypassing the borrow checker" miss the point. That's like complaining allocation "bypasses the stack".
-
Show this thread
-
Replying to @ManishEarth
(replying to the first tweet but I've read the entire thread) no, I think there's actually significant insight here. Rust doesn't JUST try to ensure memory safety. you could do that with a C compiler with sanitizers built-in. Rust also makes strong claims about ensuring…
1 reply 0 retweets 5 likes -
Replying to @whitequark @ManishEarth
semantic correctness. For example, compare Rust enums with something Go or Java would have. That Rust requires you to use indexes to implement something like ECS is absolutely a problem with the language.
2 replies 0 retweets 4 likes -
Replying to @whitequark @ManishEarth
Imagine you had a system where you absolutely, positively would not want to use heap. Something embedded. (I have such a system at work!) Then heap allocation would be a problem with the language, too, in this problem domain.
1 reply 0 retweets 3 likes -
Replying to @whitequark @ManishEarth
The difference is that absolutely-no-heap systems are an obscure corner of all software and ECS systems are everywhere.
3 replies 0 retweets 2 likes -
Replying to @whitequark
My argument is precisely that stepping out of Rust's *default* guarantees is a deliberate feature of the language and not exiting the problem domain. You're right that it's suboptimal that ECS requires this, but I don't think that's the original point.
2 replies 0 retweets 1 like -
Replying to @ManishEarth
what I'm saying, essentially, is that we as language designers shouldn't solve the problems people *think* they have ("borrow checker doesn't go far enough"), but the problems people *actually* have ("ECS are painful"). it doesn't matter if a complaint raised by a non-language-…
1 reply 0 retweets 0 likes -
Replying to @whitequark @ManishEarth
designer doesn't make sense from language design POV, if it highlights a real pain point, it is valid.
2 replies 0 retweets 1 like
And it is our job to see through all that, and at least acknowledge it, and maybe fix it if we know how.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.