TWiR quote of the week


#543

What we’ve seen is a huge shift in our capacity to make point releases, rather than a shift in the necessity of making point releases. This doesn’t seem to me like a cause for concern.

@withoutboats on internals

A good nugget on the reason for the (percieved) increase in point releases recently.


#544

References are not pointers, but temporary locks on data.

(Kornel in Cannot move out of borrowed content take 2 )


#545

matklad in the internals forum


#546

Felix91gr summarizes the (lack of) difference between C++ and Rust


#547

I love the language. And I actually feel like I’m more productive in it than in other languages.


#548

It seems to be a good week for Rust-is-great one-liners :slight_smile:

@worik sharing his experience of learning rust :heart:
(The entire post is a gem, really capturing the rite-of-passage of fighting with, then learning to love, the borrow-checker)


#549

We put in a lot of work to make upgrades painless; for example, we run a tool (called “crater”) before each Rust release that downloads every package on crates.io and attempts to build their code and run their tests.

What is Rust 2018?

Kinda amused me – imagine any language trying to compile every package in its ecosystem. Brb downloading the internet.


#550

We tend to be conservative with these kinds of things at first. We could and may change this in the future, but once you do it, you can’t go back. It’s better to be conservative, feel where the pain leads you, and improve, then to speculate on things and end up adding bad stuff. – Steve Klabnik, on adding a feature to Rust

https://news.ycombinator.com/item?id=17674155


#551

I like quininer’s ‘quote’ :

cargo build --features post-quantum

(https://github.com/quininer/ene)


#552

@cuviper sums up Rust’s value-add for parallel programming in Parallel problems to showcase Rust features


#553

Josh Triplett on #design (Discord) finding the optimal solution for one of my coming RFCs:

eddyb: cc @centril we found your syntax
JoshTriplett: IMO use replaces path while keeping the meaning, but changing from a noun to a verb, allowing the introduction of “can” which conveys allowance
JoshTriplett: Ah, I see. So, #[cfg(can_has(cheese::burger))] then? :smiley:

https://discordapp.com/channels/442252698964721669/443151225160990732/477902071455023114


#554

Turns out that shared ownership is hard when you actually have to, you know, care about it and not just wave your hands and go, “THIS IS PROBABLY FINE” as I do in…erm…other languages. :slight_smile:

(zachlute on IRC, #rust-beginners)


#555

@kornel on the new crates.rs categorization logic :heart: :cat: :dog: :heart:


#556

A poem, courtesy of @varkor:

Bastion of the Turbofish

Beware travellers, lest you venture into waters callous and unforgiving,
where hope must abandoned, ere it is cruelly torn from you. For here stands
the bastion of the Turbofish: an impenetrable fortress holding unshaking
against those who would dare suggest the supererogation of the Turbofish.

Once I was young and foolish and had the impudence to imagine that I could
shake free from the coils by which that creature had us tightly bound. I
dared to suggest that there was a better way: a brighter future, in which
Rustaceans both new and old could be rid of that vile beast. But alas! In
my foolhardiness my ignorance was unveiled and my dreams were dashed
unforgivingly against the rock of syntactic ambiguity.

This humble program, small and insignificant though it might seem,
demonstrates that to which we had previously cast a blind eye: an ambiguity
in permitting generic arguments to be provided without the consent of the
Great Turbofish. Should you be so naïve as to try to revolt against its
mighty clutches, here shall its wrath be indomitably displayed. This
program must pass for all eternity, fundamentally at odds with an impetuous
rebellion against the Turbofish.

My heart aches in sorrow, for I know I am defeated. Let this be a warning
to all those who come after. Here stands the bastion of the Turbofish.


#557
note: downstream crates may implement trait `std::clone::Clone` for type `&mut _`

rustc, via eddyb


#558

I agree with the goal, I just think it is impossible. Not that this has ever stopped anyone in Rust land

–Ralf Jung


#559

Zeitgeist of Rust: developing load bearing software that will survive us.
– Bryan Cantrill: The Summer of RUST (1:08:10)


#560

.expect("this will work if the computer isn't a coward")

Credit to @elomatreb@social.elomatreb.eu on Mastodon


#561

Sometimes bad designs will fail faster in Rust

Catherine West @ Rustconf


#562

Rust beginners worrying about lifetimes is like kids worrying about quicksand. Both turn out to be a non-issue in life.

frequentlywrong at a discussion about NLL