TWiR quote of the week

In a way [Arc and RefCell] are allowing you to escape the single ownership principle, so I don't feel calling them escape hatches is a problem.

Raw pointers on the other hand... they aren't anything like hatches at all. More like the three ghosts of memory unsafety past, present and future, willing to haunt you and your users if you give in...

-- llogiq @

(Sorry for putting up two in rapid succession, but llogiq is being particularly poetic today.)


If other compilers are insufficiently advanced, rustc must be called insufferably advanced.


Macros are not compiler magic. They are compiler science.

-- /u/DannoHung @


When I'm programming, I prefer to do my own swearing. I don't want the compiler telling me "Did you mean $#&@foo instead? (line 56)."

shponglespore on reddit


Hi, I read TWiR 364's QotW, follow the link and see a response (to the quote) that said:

Yeah I keep editing and building until it builds successfully. After that, whatever’s wrong is the compiler’s fault.


I think the quote in TWiR 364 is not (very) good.

1 Like

I'm not sure what you intend to accomplish by saying that here.

People put up proposed quotes here and others like them to vote for them on their own merits. What do replies that weren't proposed for inclusion into TWiR have to do with the suitability of the snippet that was proposed?

If it helps, QOTW isn't specifically quotes about Rust, but quotes the Rust community liked that week. See, for example, QOTW 330, QOTW 312, and QOTW 298.


i just spent 8h finding a mutability bug and now i wanna be a catgirl

By @castle_vanity on Twitter


The code people write is first a question to the compiler, and later a story for people changing that code.

– Esteban Kuber (answering to a discussion of his previous Quote of the Week) on r/rust


I know rustc is famous for its nice error messages, but i was still surprised when i found this in a github issue discussion regarding a performance regression:

I know noting about the compiler internals but it looks to me as if 90% of the time is spent pretty-printing LayoutError.

@pftbest on github


Let’s be clear: We understand that we are net beneficiaries of the exceptional work that others have done to make Rust thrive. AWS didn’t start Rust or make it the success that it is today, but we’d like to contribute to its future success.

Submitted due to this comment. From here.


I've been watching Rust closely, doing some casual learning and lurking. I've been nothing but impressed, with very few exceptions, and where I've had doubts those have been addressed in a thorough and encouraging way. To call me a cynic is to call water wet and bulls mean, so take that for what it's worth.

The community is very notable though. The community has been knowledgeable, understanding, gentle, kind, and thoughtful in their approach. The human things are done in a very human and inviting way, exceptionally so.

This tips the scales for me as far as intellectual investment goes...I now know what language I'm going to be getting to know very well for probably decades to come.

Hello Rust.