TWiR quote of the week


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


“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


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

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!


@llogiq and /u/so_you_like_donuts on

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)


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



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



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


EDIT: Actually from @llogiq

@steveklabnik on twitter:


@ubsan on IRC:

<ubsan> playbot: String::<>::new::<>()
<playbot> ""
<ubsan> All types are generic; some are more generic than others.


That’s actually from my latest blog entry.


D’oh, my mistake. I’ll edit to add the correct attribution


04.1407 * KiChjang wonders why jdm isn’t in owner status
04.1408 < jdm> ownership is a tool used by the fat cats of industry to oppress us
04.1408 < KiChjang> no, ownership is used to save us from segfaults

servo IRC, showing us the difference between Marxist and Rustacean philosophy.


the point of pointers is to point to what pointers point to

Xion on #rust-beginners IRC at 2016-05-06 19:10:57UTC+0000


@bors one of us is gonna give in, and it’s not gonna be me

@alexcrichton on Github


I’d just like to interject for a moment. What you’re referring to as rustc, is in fact, LLVM/rustc, or as I’ve recently taken to calling it, LLVM plus rustc. rustc is not a compiler unto itself, but rather another frontend of a fully functioning LLVM compiler made useful by the LLVM IR, optimizers, and code generators comprising a full compiler.

@XMPPwocky on #rust-offtopic IRC


I assume this is a reference to Gnu/Linux.


Correct, but it was in reply to my noticing that the rust repository has twice as much C++ code as Rust code thanks to LLVM. :stuck_out_tongue:


An analogy would be that Mat4x4 is a waffle iron, and Mat4x4<f32> is a waffle that comes out of it. If you are served the waffle iron (with maple syrup on top, of course) you will likely be disappointed!

Matthieu M. explaining the meaning of type Mat4x4<T> = [T; 16];


“It takes decades to learn the value of a lifetime, but @rustlang at least lets us know the lifetime of a value.”

@llogiq on Twitter