What's everyone working on this week (1/2017)?


A Rustic new year for all of you! What are you folks up to?


Gradually adding new features to my Parallel implementation to compete against the GNU implementation. I am currently trying to implement at least one feature from my todo list a day.


I’m going to further implement a small utility for the League of Legends api.

@mmstick How do you get the LoC badge? Is it updated live?


Tokei, a Rust project that counts lines, also hosts a LoC badge service that is updated live. In example:


It seems that the server caches results for projects that have been previously searched (took a while to generate the badge for Linux, but now it won’t need to be re-generated until git changes occur).


I’m working on getting crates that use pkg-config converted to use metadeps to write those dependencies declaratively in Cargo.toml, prioritizing crates most likely to appear in the dependency trees of Rust applications we want to package for Debian. (I’d love some help with this, given the number of crates involved. The main challenge involves figuring out the correct minimum version of the native library that the crate requires.)

I’m also working on adding support for metadeps in debcargo, to automatically generate appropriate dependencies on native packages corresponding to those declared pkg-config dependencies. That’ll make it possible to package -sys crates without any special-cases.

And finally, I’ve followed up on RFC 1707, expanding it to allow crates to declare versioned dependencies on tool:rustc as well as tool:cargo.


Hitting the RFCs this weekend! I’ve got some pointers from @josh to follow up on field defaults, and want to get the content for non-static type ids ready to propose.

I also started messing around with FFI for the first time this week, as a way to play with some of C#'s experimental new memory APIs (spoilers: they demonstrate why Rust’s &'a references are so amazing).


I wrote an ugly piece of Rust and suddenly, all videos from Air Mozilla are on Youtube.

Still, I think this piece of code is interesting to see how the builder pattern can be combined with SAX parsing.


I’m trying to learn Rust.

(But I’m not sure why I shouldn’t just have C++ with undefined behaviour and then let the OS (sandbox) not write it trojans to disk and not ddos the internet. I’m questioning my whole perception of whether I need to learn Rust (because it’s so different.) I’m just unsure if anyone will care that my software is “formally free” of undefined behaviour.)


Learning Rust by working on a simple 2D Piston game (with a soundtrack :musical_score:) called rust-belt.


A sandbox will only protect the rest of the system from your wayward application (and as pwn2own shows yearly can be broken, too), whereas memory safety & lack of UB make it possible to write code that cannot trivially be exploited.

Really there’s no reason a sandbox wouldn’t work with Rust, too.


Juggling work on Xtensis at the moment, and my college assignments. Hard to decide which one comes first XD :slight_smile:

(I should really look into time management techinques…)


Learning rust by rewriting my information retrieval side project. Also, I’m learning an algorithm a day and implementing it in rust. That’s been real fun, I recommend it.


Parsing Skyrim savegame files with nom and learnig rust as I go.


A library named Ripin-rs that can evaluate Reverse Polish Notation.


Today Visual C++ showed me that a sandbox would also not protect me from mystery bugs that stop development completely. I shall not execute 0xffffffff it said. So happy to be learning something better with Rust.