TWiR quote of the week

[steffahn]

I needed to double check but apparently, this identifier is actually literally valid.

Well, it gives a warning at least

warning: identifier contains uncommon Unicode codepoints

[mbartlett21]

@m51

This. Every time a post begins: "I am new to Rust and am writing a linked list..." you know it won't end well.

This one by @m51.

[tuxmain]

Linux Fortune: (full text)

What they say:                  What they mean:
Meets Tough Quality Standards   It compiles without errors.

Ok this was not about Rust. It was a joke about languages like C. But with Rust, it's true!

[josh]

Shameless self-nomination:

When a panic has a payload that's an object which needs Drops,
And the panic hits a catch_unwind for unexpected stops
Before if its Drop panicked we'd just crash to your desktops,
Now the payload gets forgotten, and you'd better grab some mops!

-- https://twitter.com/josh_triplett/status/1407776002973986819

[jonah]

What is you elevator pitch for Rust?

One thing I like about Rust is that it filters out lazy/sloppy thinkers. Even when I disagree with another Rust programmer, there is a certain level of respect that comes from knowing that they thought about the problem deeply enough to pass the borrow checker.

[CAD97]

@CAD97

[The Rust community] encourage[s] people to spend the effort to learn and benefit from Rust, [and doesn't] put down those who [fall] short on their first attempt.

Seems worthy enough of a self-nomination.

[mbartlett21]

@Ethindp

As a Rust programmer who's been using Rust for a few years now, I can say, without a doubt -- no, indubitably -- that Rust has made me a far better programmer. I can read C code and think about whether its safe in the context of what I know about what the Rust compiler might say if it looked at the code I was reading. The ironic thing about my transition to Rust is that its actually harder for me to write C/C++ properly now because I feel like its almost... Alien if you will. When I write the code, I think a lot about its safety and correctness and I'm always looking for ways I can make it better.

By @Ethindp.

[aDotInTheVoid]

Beginning Rust: Uh why does the compiler stop me from doing things this is horrible

Advanced Rust: Ugh why doesn't the compiler stop me from doing things this is horrible

qDot on Twitter

[quinedot]

The nasty thing about UB is that it does not guarantee that things will go horribly wrong. UB likes to lure you into thinking that you are fine... until it suddenly pulls the floor out from underneath of you and you plummet into the pit where all your code has been arranged in a nice set of spikes.

RalfJung on IRLO

[chrefr]

@aDotInTheVoid

Beginning Rust: Uh why does the compiler stop me from doing things this is horrible

Advanced Rust: Ugh why doesn't the compiler stop me from doing things this is horrible

qDot on Twitter

Just replace the "Advanced Rust" with "Beginner C" (or "Advanced C", for that matter) and this will be perfect

[RalfJung]

Lol I came here because I considered self-nominating, but you people are too quick and exceedingly well informed.

[Havvy]

First of all, it seems like Pin might actually be Unpin . This might sound surprising, but really what Unpin means is that the "pinned" and "not-pinned" typestates of a type are the same

-- ralfj

Source: https://github.com/rust-lang/rust/pull/81363#discussion_r650561252

[jonstodle]

If I can get around ownership issues by cloning first I will absolutely do it, because I see removing clones as an optimization step. […] go and actually measure your performance to see if you actually need to remove the clones. Sometimes you don’t and sometimes you do.

-- Jonathan "JT" Turner in a Rust stream

[Kestrer]

Tip: whenever you wonder if Pin could be the solution, it isn't

• @SkiFire13 on the official Rust Discord

[RustyYato]

One of the hardest parts of design is the way it interacts with everything. A good abstraction can sometimes cut through that tangled mess and make some parts orthogonal.

@Eh2406 on internals

[josh]

"Four years had passed since then and the future was now; two years have passed since the future was now and the future is now past."

-- bstrie in Scoped threads in the standard library, take 2 by bstrie · Pull Request #3151 · rust-lang/rfcs · GitHub

[hetoug1]

We were able to verify the safety of Rust's type system and thus show how Rust automatically and reliably prevents entire classes of programming errors

Ralf Jung in Computer Scientist proves safety claims of the programming language Rust | EurekAlert! Science News

[aDotInTheVoid]

Rust isn't a "silver bullet". Never was. It is a car with seatbelts, airbags, lane assist, turn signals and crumple zones. You can still crash, but risk is mitigated.

Estaban Kuber on Twitter

[Mokuz]

Rust is an super-safe self-driving car with manual override.