Gankro

26 ms·

211.
by Gankro 11y ago
Note that this is only something you really need to think about when writing `unsafe` code, which basically unlocks a whole new set of rules that you need to worry about (zero-sized types in offsets, manual allocations, safety boundaries,
212.
by Gankro 12y ago
raw strings: https://github.com/rust-lang/rust/blob/master/src/grammar/ra...
213.
by Gankro 12y ago
Usually if this happens, it's a good hint that this piece of code could use a good comment. Not always, of course.
214.
by Gankro 12y ago
Huh. I thought it was basically a bijection, though?
215.
by Gankro 12y ago
In addition to what aturon said, for actual patches these are the people who decide on merging: https://github.com/orgs/rust-lang/teams/rust-push Maybe a third to a half are Mozilla employees (although it&#x2
216.
by Gankro 12y ago
pcwalton, at least, has mostly been focusing on making Servo completely amazing. Not a lot on the rustc front these days. Sucks for us, great for Servo. (because pcwalton is fantastic)
217.
by Gankro 12y ago
Oh hey! This is primarily authored by one of my supervisors. It's my go-to source for reviewing basic analyses and implementation details. Totally worth the read!
218.
by Gankro 12y ago
"Oh I'll make this one shorter by breaking it into two parts" > 3100 words Fuck.
219.
Building a HashMap in Rust – Part 1: What's a HashMap?(cglab.ca)
6 points by Gankro 12y ago|3 comments
220.
by Gankro 12y ago
Eh, with the new oprhan/impl rules associated and uh... not... associated(...?) types have developed quite a schism.
221.
by Gankro 12y ago
Like three different kinds, too! // Old-style generics; monomorphized // with S as an "input" type of MyTrait fn foo<S, T: MyTrait<S>>(elem: T) { ... } /&#x2
222.
by Gankro 12y ago
There have been a few proposals for advanced bit-packing stuff, but most of it has been postponed as back-compat for later. That said, by default enum/struct layout is undefined, so it's possible the compiler could be taught to op
223.
Rust Collections Case Study: BTreeMap(cglab.ca)
9 points by Gankro 12y ago|0 comments
224.
by Gankro 12y ago
The 1.0 stable release will be pushed back as far as is deemed necessary. Ideally it will be in 14 weeks, but if there's still critical work to be done when we hit that point, we'll wait another 6 weeks. And another. And another.
225.
by Gankro 12y ago
It's only a breaking change to one's API to actually use the functionality, though. I don't think there's anywhere in std's public APIs where we would suddenly change from returning a concrete iterator to an &qu
226.
by Gankro 12y ago
Buildbot and Bors are also hosted on Github. :D https://github.com/rust-lang/rust-buildbot https://github.com/graydon/bors/tree/rust
227.
by Gankro 12y ago
There is a blah/rss.xml, but yeah that's on my TODO. Maybe for the next post.
228.
by Gankro 12y ago
Well I mean if you want to cheat with iterator adaptors you can just use min_by: http://doc.rust-lang.org/std/iter/trait.IteratorExt.html#tym... :P (shhh I was tired and trying to come up with a simple but moderat
229.
by Gankro 12y ago
And I completely forgot about how they can be used to give collections "chunks" of code to run without the need for function pointers! And how you can use unboxed closures with no captures to make a zero-sized bundle of static-dat
230.
by Gankro 12y ago
Fixed. Although for some reason geddit froze up trying to save and it was briefly So Much Worse.
231.
by Gankro 12y ago
Done.
232.
Rust, Generics, and Collections(cglab.ca)
187 points by Gankro 12y ago|10 comments