TWiR quote of the week


#27

kmc: “Rust follows semver. The major version number is the 160-bit integer corresponding to the object ID of the head git commit on master.”

https://www.reddit.com/r/rust/comments/2z9u9v/this_week_in_rust_74/cpha1lr


#28

http://logs.glob.uno/?c=mozilla%23servo#c186735

<Savago> I have the gut feeling that some of this crazyness could be fixed if ImageCache went through an overhaul.
<Ms2ger> Congratulations! You own the image cache now


#29

The motto of pretty much every “web” technology should be: “It seemed like a good idea at the time”

That, or “For legacy reasons”

From a /r/rust thread on html5ever.


#30
<mbrubeck> the 5 stages of loss and rust <mbrubeck> 1. type check. 2. borrow check. 3. anger. 4. acceptance. 5. rust upgrade

#31

The borrow checker is a real tsundere. She’s cold and harsh about the
mistakes you initially commit in your code, but she’s a real sweetheart
for pointing at all the wrong things in your code. It’s just too bad
that some people don’t have the patience to warm up with her for a bit.
There’s quite a bit of dere in the borrow checker.

faithfuldoge via reddit


#32

TWiR is fast approaching!


#33

i was wondering, somewhat seriously, whether you actually do want to use the generic methods for
everything. as_ref::<[_]>() is almost graphically shark-jumping

- @aturon on #rust-internals


#34

Diagnostics are the UX of a compiler, and so they’re deserving of the exact same care that is put into mobile app or Web design.

@pcwalton on HN.


#35

@frankmcsherry on #rust:

<frankmcsherry> rust is like a big bucket of solder and wire, with the promise that you can’t electrocute yourself.


#36

mwu in #servo

< mwu> I am about 2 errors away from rust’s next pile of errors though


#37

Bump. A new TWiR is nearly upon us!


#38

bstrie on #rust-internals:

Saraswat made the rules, we just enforce them :P

#39

unsafe restricts which code could contain undefined behavior, but it doesn’t isolate the effects of that undefined behavior.

https://www.reddit.com/r/rust/comments/32wqa7/wip_llamadb_a_simple_sql_database_written_in_rust/cqfoh41


#40

@aturon on backward-compat wizardry:

<aturon> i was backed into a corner, magic was the only choice

https://botbot.me/mozilla/rust-libs/2015-04-21/?msg=37174624&page=2


#41

From https://github.com/brson/httptest#3-routes:

I first try let payload = request.body.read_to_string(); because I know it used to work.

It does not work.


#42
23:37 < geofft> time flies when you're having fn()

#43

mbrubeck 12:04 AM: “Rust: A minute to learn, a lifetime to master.”


#44

Not funny, just on point.

< Ms2ger> And note, unsafe code isn’t for violating Rust’s invariants, it’s for maintaining them manually

#rust irc.


#45

Awesome quotes this week. Thanks everybody!


#46

Ultimately, I think this all boils down to the fact that borrowck only cares about reachable
values. A leaked value isn’t reachable, therefore it doesn’t matter
that it had a lifetime associated with it and technically outlives that
lifetime, since it’s not reachable no undefined behavior can be invoked.

Great insight by kballard on the safety of leaking