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 4 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
I mean, it’s kind of a problem, but it’s not a problem in the sense that I think we did the wrong thing. I don’t see a solution other than having a type system that allows you to prove graph properties, probably a dependently-typed one.
2 replies 0 retweets 3 likes -
Replying to @pcwalton @ManishEarth
yes, I do not mean to say here that Rust does a wrong thing. I'm saying that the complaint is a valid pain point, not the complainee not understanding something.
1 reply 0 retweets 5 likes -
Replying to @whitequark @ManishEarth
Yeah, I agree that it’s a valid pain point. Type systems that can prove things about doubly linked graphs are so gnarly right now… wish there were more practical work in this area :\
1 reply 0 retweets 3 likes -
Replying to @pcwalton @whitequark
I'm surprised these exist at all tbh and would like to read more
1 reply 0 retweets 0 likes
-
-
-
Somehow my brain parsed all occurrences of "Alga" as "Agda" in those two tweets and I was super confused.
0 replies 0 retweets 2 likes
End of conversation
New conversation -
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.