@bors one of us is gonna give in, and it’s not gonna be me
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.
An analogy would be that
Mat4x4is 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!
“It takes decades to learn the value of a lifetime, but @rustlang at least lets us know the lifetime of a value.”
Fishing for the quote of the week again?
Slade (a.k.a. Argorak) on twitter
Sorry, I can’t find it on Twitter. Link?
*cough* …of a type *cough*.
That would have broken the symmetry.
Added the link.
Rust is like doing parkour while suspended on strings & wearing protective gear. Yes, it will sometimes look a little ridiculous, but you’ll be able to do all sorts of cool moves without hurting yourself.
llogiq on reddit
I love how we started out having intractable debates about the feature itself, and now we’ve graduated to the meta level and started having intractable debates about how to even begin moving forward on the original intractable debate. I propose we now move this to the next level™ and have a debate about the process by which we shall decide which parts of the feature set we will debate first.
@glaebhoerl on the
impl Trait RFC https://github.com/rust-lang/rfcs/pull/1522#issuecomment-222382210
/r/SimonSapin describing the Rust development process in two characters
I’ll nominate this bit from my own RFC, because I crack myself up every time I read it:
Since this RFC promotes including this section, it includes it itself. (RFCs, unlike Rust
enumtypes, may be freely self-referential. No boxing required.)
@steveklabnik’s response to rust being too hard:
I believe in people.
The Rust standard libs aren’t quite batteries included, but they come
with a pile of adaptor cables and an optional chemistry lab.
#rust just now.
<Makoryu> Binero: But does the overallocation happen in Vec, or in the allocator itself <Binero> It has to be in vec as the allocator doesn't return anything exposing if it overallocated. <Ketsuban> If the allocator doesn't tell you if it overallocated or not, how do you know it didn't overallocate? 8) <_habnabit> checkmate, athiests
(I swear I didn’t plan this ahead of time.)
FOR THE LOVE OF ALL THAT’S NOODLY, LET THE COMPLETIONS FLOW.
/u/herbadah in this weird thread about Racer
<ketralnis> Rust is also really phobic of heap allocations […] <Xion> Yes, Rust encourages everyone to be a full stack developer :)