TWiR quote of the week

I particularly liked this interaction between /u/reyqt and @steveklabnik:

/u/reyqt: It will be fine until compiler complain [sic] about your code

@steveklabnik: "describe rust in one sentence"


Rust helped me grasp concepts I should have known when writing C++

-- Microsoft intern Alexander Clarke in this blog post:


Slightly off-topic, but I've had the experience in the exact opposite direction: having written lots of C++ and having been constantly looking for improvements and patterns that ensure safety, Rust had basically no learning curve for me.


As the intern honestly admits in that blog, most users of high level languages have no idea where the memory is they are using and who else is using it. It's not something they think about until they get the segfaults and corrupt data.

Can't blame them. The whole thrust behind high level languages since forever has been to abstract away all those annoying details. Works fine in Javascript but it's an abstraction too far in the case of C++.

Memory in C++ is a leaky abstraction (see what I did there :slight_smile: )


I came from C# where I found that low level memory things were kind of swept under the rug and left to the compiler to deal with. These kinds of things interested me so I tried C++. To put it simply, I was not prepared to deal with C++, so I instead switched to Rust, and have found that dealing with the details of low level things can be nice and refreshing little niches, opposite to my experience in C++ and present compared to C# (At least at the time and my understanding of it).



let txt = child.expect("this is safe")
    .get_text().expect("this is safe");

…man, starting to dig through the source code of a really large open source program is so weird. It’s like wandering around a giant cathedral that’s being constantly renovated and repaired and maintained over the course of years by a giant team of invisible crafters and architects, who mostly communicate via notes and designs pinned to the walls in various places.



Woah, I just came here to suggests this. I'm only half surprised someone else has before.

Aaaaaa I wrote an article because of a quote in TWiR and now a quote from it is being submitted to TWiR!

Mind blown.


Question on community discord:
Well, what is the difference between:
let closure = |_: Id<'_>| {}

let closure = |_| {}

Answer by Ari:

One is a closure, the other is a toilet


I'm never gonna ask that question again... Oh, and I can't unsee it now, thanks y'all

1 Like

I can't tell which one is which?

From Writing "fluent" code, creating objects with reference to self and lifetime subtyping


From std::marker::PhantomData and unused fields in structs:


Rust and rustaceans being what they are, if you say „performance“ you can expect few crates to pop up.



I know the closest connection this has to Rust is being in a blog post that's a response to Gankra's "Text Rendering Hates You", but it's just so good:

In my experience, prayers are not a very effective concurrency primitive.


there are two hard problems in computer science:

  1. writing software that isn't in rust
  2. naming things



Quite so.

I suspect naming things should be number 1 on the list. Even Rust does not help us with that.

We've previously had QotWs that weren't specifically about Rust, haven't we? I think that's actually a good thing; QotW are quotes the community "likes", which should arguably say more about the community than about Rust the technical project.


If being directly relevant to Rust is not required my quote of the week comes from Russell Anderson in some video about some kind of programming on YouTube I found last night:

I can make software, without knowing, whatever it is that I'm doing.

He was talking about the subtleties of Javascript. It rang true with me as I seem to have spent my life making software with a new language, operating system, application area every two years or so. Now Rust of course. Permanently in a state of not knowing, whatever it is, that I'm doing :slight_smile: