Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us an email! Want to get involved? We love contributions.
Updates from Rust Community
News & Blog Posts
- Design patterns in Rust.
- Managing connection state with mio.
- Writing an OS in Rust.
- Good practices for writing Rust libraries.
- Rust and Swift.
- This week in Redox 3.
- This week in Servo 38.
- Things I learned from Rust.
- Messy error handling in Rust with
- [podcast] New Rustacean podcast episode 02. The
structdata type constructor, and the basics of Rust's "ownership" concept and "borrowing" and "moving".
- [podcast] New Rustacean podcast episode 03. Enumerated (
enum) types, pattern matching, and meaningful return values.
- Simple_parallel 0.3: Revisiting k-NN.
Notable New Crates & Projects
- Rust OS comparison. A comparison of operating systems written in Rust.
- Nucleon. Dynamic load balancer written in Rust.
- Typenum. Compile time numbers in Rust.
- Pumpkin. A cryptographically secure prime number generator.
- Brotli-rs. Brotli decompression in pure, safe Rust.
- Multirust-rs. A reimplementation of multirust in Rust.
Updates from Rust Core
101 pull requests were merged in the last week.
See the subteam report for 2015-10-23 for details.
- Implement RFC 1229: Turn statically known erroneous code into a warning and continue normal code-generation.
- Move desugarings to lowering step.
- Cargo: Implement
- Add the PNaCl/JS targets to the backend.
- Implement drain over a range for
- Owned conversions for CString.
- std: Stabilize library APIs for 1.5.
- Bryce Van Dyk
- Chris Drake
- Emanuel Czirai
- Irving A.J. Rivas Z.
- James McGlashan
- Lee Jenkins
- Michael Howell
- Philipp Oppermann
- Stefan O'Rear
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
No RFCs were approved this week!
Final Comment Period
- Allow overlapping implementations for marker traits.
- Promote the
libccrate from the nursery.
- Enable the compiler to cache incremental workproducts.
- Add some additional utility methods to
- 10/27. Dinner at Tied House.
- 10/28. Columbus Rust Society.
- 10/28. Rust Amsterdam.
- 10/28. RustBerlin Hack and Learn.
- 10/28. Rust Meetup Cologne
- 10/31. Rust Meetup Tokyo.
- 11/2. Women Who Code, Codemotion Berlin.
- 11/4. PDXRust.
- 11/9. Seattle Rust Meetup.
fn work(on: RustProject) -> Money
No jobs listed for this week. Tweet us at @ThisWeekInRust to get your job offers listed here!
Crate & Quote of the Week
@retep998 has, by and large, taken it upon himself to try and bind the Windows API using the sadistically horrible official
windows.hheader. By hand.
Having chipped away at the surface myself, let me tell you some of the horrors I've seen.
windows.hcontains sub-headers that implicitly depend on other headers having been imported in a particular order. Get the order wrong, and the definitions change. This makes isolating anything, let alone defining where it canonically is supposed to come from a Sisyphean task. It contains symbols that are deliberately defined multiple times. Sometimes, with different types. Sometimes, with different values. Because
windows.hwas written by shambling horrors from beyond time and space. That's not even touching the titanic, C'thuloid mass of brain-twisting agony that is the conditional compilation definitions and annotations sprinkled throughout like some kind of virulent pox. There are obscure conditional flags that change or omit functions based on bizarre edge cases buried in some obscure file which is included three different ways by paths so obtuse you could make a credible argument for a satellite map of the damn thing except it'd have to be a six dimensional monstrosity that would drive you mad just from looking at it. Then there's the vast tracts of API surface that are exposed via COM which Rust does absolutely jack toward making in any way usable so you have to write the damn vtables by hand and heaven help you if you run into an interface with multiple base interfaces because at that point you might as well give up and just use C because at least that has an IDL generator for it. That's even before you realise that LLVM's code generation isn't even correct on Windows, and this whole time, it's been silently generating bad code for stdcall methods which you'd think would be just like functions but nooo that's now how Visual C++ works, so methods with particular return types are incompatible at the binary level, unless you know about this and manually correct for it by fudging the type signatures in the Rust binding code and really it's no wonder he's a rabbit because a human would have been driven so deep into madness they'd need be halfway to the Earth's firey core.
To put it another way: I think it'd be kinda nice to give him a proverbial pat on the back for his herculean efforts thus far.