TWiR quote of the week


#403

<kmc> Rust std library has a type called Cow
<alixir> seems useful
<alixir> to avoid Mooving data unnecessarily


#404

Which channel?


#405

PM; got permission.


#406

Manishearth: eddyb: IMNHTHAHAHAHAHAHAHAHAHAHAHA
Manishearth: ^ the creators of rust inventing borrowck in their evil lair

From #rust-internals


#407

For the most unsound Clone implementation ever…


#408

“Have I ever told you the story of the mutpocalypse? It all began fifty years ago…”

Moooom! Grandpa Gankro’s telling that story again!”

“He’s old, just humour him.”

Quxxy on Reddit


#409

Because mem::transmute is the answer for all the borrow checker complaints! (Not really)

L117: I tried to change my nickname to meme::transmute::<&'a Doot, &'static mut L117>(doot) with no success ):
Cldfire: Your plot to live forever has been foiled


Spookin’ Dootin’ mem::transmutin'

Or

Angry Dootin’ mem::transmutin'


#410

@enet_4: Day 31: I have gained the linter’s trust. Clippy still thinks I’m a format string.

http://chat.stackoverflow.com/transcript/message/37742376#37742376

Due to https://github.com/Manishearth/rust-clippy/issues/1706 linting on panic!({ true }) about a malformed format string.


#411

Hi, I think rust is just an amazing achievement because it is the first time we all, just about the first time we’ve seen one of these kind of linear or affine type systems actually make its way into practical use. So its just incredible, well done! I’m, you know, I mean I’m wild with envy. I want to steal all the best ideas I can and put them in Haskell.

Simon Peyton Jones commenting on Niko Matsakis’ presentation about Rust at Curry On Barcelona! YouTube link.


#412

@CleanCut in the sibling thread gives the best metaphor for Rust I’ve seen so far :slight_smile:


#413

(quoting Effective Modern C++ by Scott Meyers)
"The interaction among perfect-forwarding constructors and compiler-generated copy and move operations develops even more wrinkles when inheritance enters the picture."
This is the kind of sentence that will make me run away screaming. Rust doesn’t have any of those features, gets by fine without them, and thus avoids such bizarre interactions.

“Keegan” on his blog, main is usually a function


#414

This should be the quote of the week, obviously.


#415

The quote content from the previous post:

That RFC would break too much code to justify implementing it in Rust 3.0. @SimonSapin


#416

Quoted from https://air.mozilla.org/game-developement-in-rust/ , in the wrap-up:

[the] unsafe [keyword] is your friend. He’s not your friend like you’d invite to your sister’s wedding, but he’s the kind of friend who lives in a bunker in the wilderness has has 37 guns and if you need something blown up he is there for you.


#417

Did the presenter actually say “has has”?


#418

Spoken at 38:35 in the video.


#419

This may sound intuitively plausible, but turns out to be extremely subtle.

Ralf Jung on Rust safety in “RustBelt: Securing the Foundations of the Rust Programming Language”.


#420

Link for @sanxiyn’s quote: RustBelt: Securing the Foundations of the Rust Programming Language (page 21 of the PDF, last paragraph under point 5.2).
That turned out to be quite the interesting read about formalising the lifetimes of Rust, even if the maths went over my head…


#421

Good farmers use their bare hands, average farmers use a combine harvester.

sin2pifx’s sarcastic response to “Good programmers write C, average programmers write Rust”.


#422

In response to “What is preventing rust from replacing c/c++?”