unpopular punctuation opinion: the spanish characters ¿ and ¡ are some of the finest additions to written communication ever invented
-
Show this thread
-
getting to the end of a rust statement to find a missing ";" is like reading a long sentence ending in "?" and realising you should have read the whole thing differently
2 replies 0 retweets 19 likesShow this thread -
marks that affect the interpretation of a whole statement should appear at the beginning
3 replies 4 retweets 27 likesShow this thread -
to be clear: you are allowed to say `return expression;` in rust, but this is heavily de-emphasised in the docs I can see an argument from symmetry between functions and closures, but... I'm not feeling it, sorry
2 replies 1 retweet 4 likesShow this thread -
Replying to @mountain_ghosts
So given you know ruby I’m a bit surprised; do you dislike it there too?
1 reply 0 retweets 0 likes -
Replying to @steveklabnik
no, because the last expression in a body is *always* the return value in rust, it depends on whether it has a trailing ";" or not, which I find really unergonomic the type signatures help though; seeing "-> T" makes me look for a return
3 replies 0 retweets 0 likes
The same is basically true for Rust though. The only difference is that we use `;` instead of `\n`. The only time there's a logical difference is if you accidentally put a semicolon on the last line, in which case the compiler specifically tells you not to
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.