wait when/where was this?
stackoverflow, @shepmaster: This would be a good example of what Rust helps prevent, but you’ve
deliberately turned off the safety checks, and now we are back to C.
23:12 < chickensalad> steveklabnik: you should get free gyros for life, funded by the rust community
< reem> I’m quite interested in discovering this HTTP/2 library, but I can’t bring myself to read four paragraphs of small caps
(with regard to /r/rust’s moving CSS-enabled tribute to Terry Pratchett)
Thanks for bringing the quotes again this week!
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.”
<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
The motto of pretty much every “web” technology should be: “It seemed like a good idea at the time”
That, or “For legacy reasons”
<mbrubeck> the 5 stages of loss and rust <mbrubeck> 1. type check. 2. borrow check. 3. anger. 4. acceptance. 5. rust upgrade
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
TWiR is fast approaching!
i was wondering, somewhat seriously, whether you actually do want to use the generic methods for
as_ref::<[_]>()is almost graphically shark-jumping
- @aturon on #rust-internals
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.
@frankmcsherry on #rust:
<frankmcsherry> rust is like a big bucket of solder and wire, with the promise that you can’t electrocute yourself.
mwu in #servo
< mwu> I am about 2 errors away from rust’s next pile of errors though
Bump. A new TWiR is nearly upon us!
unsaferestricts which code could contain undefined behavior, but it doesn’t isolate the effects of that undefined behavior.
@aturon on backward-compat wizardry:
<aturon> i was backed into a corner, magic was the only choice