if 'static' is a reserved word you have already done something terribly wrong. sorry, rust
Show this thread
-
-
-
Replying to @Gankra_
yes. especially when you have `mut`, which sounds like it should be the opposite? `static mut` is total nonsense
4 replies 0 retweets 1 like -
Replying to @eevee
I think we're in a situation where globals are so messed up that they wrap back into making sense. We have `const` *and* `static`, and the only distinction is that statics are supposed to have a fixed ("static") address.
1 reply 0 retweets 3 likes -
Replying to @Gankra_
don't /most/ declarations have a fixed address? :) maybe `const` should've been `inline` and `static` should've just been top-level `let`
1 reply 0 retweets 2 likes -
Replying to @eevee
this probably isn't useful to a lot of people, but i keep them straight in my head by remember `const`s are rvalues and `static`s are lvalues (the latter of which can be mut or not)
2 replies 0 retweets 5 likes -
yes that's the official distinction but like, if you try to say "lvalue" to a user you should be arrested for lang-crimes.
3 replies 0 retweets 22 likes -
universe brain: lvalue and rvalue as keywords
3 replies 2 retweets 11 likes -
Wow, without even bothering to reserve xvalue, prvalue, and glvalue? Talk about reckless...
1 reply 0 retweets 7 likes -
reserve every identifier ending in "value"
1 reply 0 retweets 2 likes
Just reserve `value` and use subscript syntax obvs
2:51 PM - 29 Nov 2017
0 replies
0 retweets
4 likes
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.