Rust: spend your lifetime thinking about lifetimes.
Failure is not an OPTION<T>.
It’s a Result<T, E>.
winapiis big. Really big. You just won’t believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it’s a long way down the road to the chemist, but that’s just peanuts to
cargo docwas designed, they did not forsee
winapi. They did not believe the legends. The warnings.
But now, like the Cygnus, caught in the pull of a black hole, all we can do is fall. Fall into darkness.
u/Quxxy on r/rust (suggested by u/jswrenn)
Seeing this just after a now-deleted-for-inappropriate-tone example in the discussion around RFC 2308 (which mentioned a 330-variant enum in SPIR-V) made a half-formed draft of the following come to mind:
Rust: The Murphy’s Law language for programmers tasked with works both subtle and powerful.
(I had to ad-lib the “tasked with works both subtle and powerful” part because I couldn’t google up whatever reference was tickling my brain.)
Rust has a very high friction coefficient.
We call it grip and it lets us drive fearlessly around hard corners very fast.
Even though it’s an obvious typo, I must nominate @droundy’s statement about eternal love:
If a panic or exit happened in the loop, then the variable would not love forever.
I’m very happy that Rust saves us from such dire consequences.
Rust’s standard regex library isn’t the fastest in the world, and the lack of backtracking can be limiting, but it is highly optimised for Rust’s main use case of posting showoff comments on Hacker News.
QuietMisdreavous on removing hoedown from rustdoc (link):
Begone, demon of the foul C! Your presence is no longer wanted here! With this strike, I commit you to the depths of history, never to torment our fair land again!
As found in the commit (cur 5bd5bc3):
Is it really time? Have our months, no, years of suffering come to an end? Are we finally able to cast off the pall of Hoedown? The weight which has dragged us down for so long?
(By the way
&Tshould be called exclusive and shared references, rather than mutable and immutable, since that’s what they’re really about.)
This was rather a highly upvoted comment on r/rust I made so I thought I’d share.
The comment was made by sleepy-me and nominated by middle-of-day-me, so it’s not self-promotion, right?
No, I don’t have Dissociative Identity Disorder.
At least, that’s what I tell myself when I ask myself that question.
As an ugly workaround: change the file format, compile it with GCC and link the resulting .o, accessing it via an
extern "C"? – u/bestouff
That would work though.
If you actually had Dissociative Identity Disorder (DID), or knew someone who did, you would have written that joke as follows:
No, we don’t have Dissociative Identity Disorder.
At least, that’s what we tell ourselves when we ask ourselves that question.
This is a known issue which will probably get fixed at some point. For now, don’t do impossible things; the restaurant at the end of the universe is overrated, anyway.
<mbrubeck> 'cause I'm so Into::<You>::into(you)
I’d like to nominate @Bors this week, for its reply to previous candidate @QuietMisdreavus:
Bors replied: (emphasis mine)
Rust is so intelligent, even the build bots have a sense of humour!
…Well there are some places go[lang] can’t go, but Rust can!.. ~ Rust Nairobi Meetup Attendee
Imagine going back in time and telling the reporter “this bug will get fixed 16 years from now, and the code will be written in a systems programming language that doesn’t exist yet”.
If Rust is martial arts teacher, Perl is a pub brawler. If you survive either, you’re likely to be good at defending yourself, though both can be painful at times.