I still think unsafe was Rust's worst naming mistake because it just means "You have to handle the invariants yourself" but that's very not clear from unsafehttps://twitter.com/mycoliza/status/1006715273141841923 …
-
-
Replying to @mgattozzi
Given the biggest difference is access to raw pointers, maybe we should just name it that? raw { // Please filter carefully before consuming }
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
I mean that's part of it but I still think that handking invariants is the real thing that needs to be addressed. Usually raw pointers are laste of it but not always
1 reply 0 retweets 1 like -
Replying to @mgattozzi @yoshuawuyts
I just got up I can't believe any part of that sentence made sense
1 reply 0 retweets 1 like -
Replying to @mgattozzi
hahaha; I sorta get it I think. Curious what you mean by "handling invariants". Think I'm missing some voculary there.
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Okay so the compiler can only check so much right? Some things it can't check (like raw pointer access) and so there are rules associated with it (invariants) that you the programmer have to uphold. If you don't this leads to interview behavior!
1 reply 0 retweets 1 like
ahahaha, yeah okay that makes perfect sense! Cool :D
-
-
Replying to @yoshuawuyts
:D I forget sometimes I use short hand so thank you for asking to clarify!
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.