TWiR quote of the week


#223

Alongside assorted fixes, it enabled MIR to launch :rocket: and do a complete bootstrap.
To try it yourself, ./configure --enable-orbit or make RUSTFLAGS="-Z orbit".

From eddyb’s PR which bootstrapped MIR straight into orbit.

And the description of -Z orbit:

get MIR where it belongs - everywhere; most importantly, in orbit


#224

On Reddit:

llogiq: That feeling when you battle with borrowck and remain victorious.
mus1Kk: I’d give my firstborn to experience it once!

**Sneakily decides to leave out the “just kidding lol” part of the quote.**


#225

You should at least include my answer.


#226

Enlighten us, please.


#227

No need for a firstborn. Just keep on learning. Don’t give up, your day will come.

Me on /r/rust (for those opposed to reddit links)


#228

From IRC just now.

<phaazon> ok
<phaazon> and what trait is from from?
<jix> From :D
<phaazon> ok :D
<phaazon> so from is from From
<phaazon> nice!

#229

Rust: "C, if it were invented today by a guy who only knows Haskell." -- Eevee


#230

That quote was not produced anywhere close to this week.


#231

Quxxy wrote this, when asked why an open-ended range doesn’t stop at the maximum value of its type:

This seems like a pretty big oversight. This is totally on purpose and your own fault for telling it to run screaming off a cliff trying to count integers out to infinity. It doesn’t have that many fingers.


#232

Oh! I did not realize it had to be this week! I just searched this thread
if it hadn’t been mentioned and thought it would fit. Cheers!


#233

From @steveklabnik on #rust-community:

steveklabnik> i basically am @rustlang […]


#234

<arielby> is the obligation forest a secret plot to make typeck performance so bad
<arielby> we will need incremental compilation to work at all?


#235

“Explicitness is the fourth core value of Rust. Ironically, I don’t see
that “Explicitness” is ever explicitly stated as a goal of Rust.” – Ian Whitney, Rust via it’s Core Values


#236

Rust offers a lot of interesting tools, but they can be complex to
describe. What I’ve found is that as long as I keep Rust’s core values
in mind, I can usually figure out why it works the way it works.

Rust via it’s Core Values


#237
5:44 PM <WindowsBunny> only on linux can you experience subsecond winapi compile times

@retep998 on the topic of cfg’d-out windows crates being built on other platforms. Notably, this problem can go away in 1.8 thanks to https://github.com/rust-lang/cargo/pull/2328!


#238

@llogiq and /u/so_you_like_donuts on https://www.reddit.com/r/rust/comments/4fc6m4/from_str_to_cow/d27rv0f:

Cow is still criminally underused in a lot of code bases

I suggest we make a new slogan to remedy this:

“To err is human, to moo bovine.”

(I may or may not have shamelessly stolen this from this bug report)


#239

In general, enough layers of Rc/RefCell will make anything work.

gkoz


#240

One does not casually enter the radiation zone to adjust the wall clock for daylight savings.

Gankro on handling safe code sharing a module with unsafe


#241

@bors

nagisa submits an ambivalent review (probably not intentional) (PR).


#242

EDIT: Actually from @llogiq https://llogiq.github.io/2016/04/28/arraymap.html

@steveklabnik on twitter: