How is pipeliner different than rayon?
I only tried rayon for a short time before giving up on it. So what I'm about to write might not be accurate.
The use-case was parallelizing network requests(client side), to avoid accumulating latencies. Those requests are not CPU-bound. So, requesting multiple parallel threads on a dual core device makes sense!
Does not work with iterators directly.
It's not clear, at least from a cursory look at the docs, how to configure the number of threads used with
Errors can contain hard to decipher unsatisfied trait bounds.
Works with iterators directly.
You can pass
.with_threads(num)anywhere in your iterator chain. You can even pass it multiple times with different numbers.
Errors are easy to decipher (your typical borrow checker errors. Unsatisfied
[minor] No wildcard/glob
pipeliner may not have a fancy work-stealing algorithm implemented behind the scenes. But it provides more flexibility and easier integration with iterators.
Cargo-fuzz. Command line wrapper for using libFuzzer.
PumpkinDB. PumpkinDB is a compact event sourcing database, featuring fast on-disk storage, flexible approach to event structure and encoding, sophisticated event indexing and querying.
μtest. Unit testing for microcontrollers and other
I'd like to nominate @BurntSushi's FST crate .
This provides a very compact in-memory representation of maps, in the same ballpark as gzip, but queryable!
The compact representation makes analyses possible that would otherwise explode the RAM of even the biggest compute nodes.
In Andrew's typical style, the crate, the theory behind it, and the design trade-offs are extremely well documented via blogpost. After reading it, I felt like I had learned something new about theoretical computer science, and had a good feeling for when to use the crate.
My department is currently using the crate to analyse genome regulation, by identifying the counts of all possible 16-mers in the human genome, so 4^16 = 4.294.967.296 keys. Our algorithm was impossibly slow before we encountered FST, producing hundreds of gigabytes of temp-files that had to be processed line-by-line.
Thanks to FST we can do unbiased analysis into what makes humans tick: how our genomes are regulated.
I'll add that we're using
fst via it's python bindings, by Johannes Baiter. Johannes was supportive and quickly responded to our questions. (He works at the digitisation centre of Bavarian State Library, so I'm very curious what use-case he found for
I include this tidbit to demonstrate that there is already a (minute) user-community around
fst, and that it is (apparently) broadly applicable.
All in all:
fst is a crate that, through its great implementation, excellent documentation and great API, makes high-performance data structures available to a new audience, enabling real research and bringing humanity forward.
Andrew Gallant / @BurntSushi
duct - "A cross-platform library for running child processes and building pipelines. duct wants to make shelling out in Rust as easy and flexible as it is in Bash. It takes care of gotchas and inconsistencies in the way different platforms shell out."
Serenity - "Serenity is a Rust library for the Discord API. It enables you to create awesome bots for the Discord chat service in an easy and organized way."
pretty_assertions - "Overwrite
assert_eq! with a drop-in replacement, adding a colorful diff."
pretty_assertions for making it into TWiR 175!
As a happy user of fst without any further involvement, I hope I'm not violating etiquette by re-nominating
Please tell me if I'm overstepping!
fst a few hours after TWiR 174 came out, because 174 didn't have any crate "for lack of nominations". I can understand my suboptimal timing may have caused it to accidentally not be considered for 175.
I'd say 12 collected likes (at time of writing) is enough show of support to give it a rematch for 176.
I've used fst and it's great.
I would like to nominate Official Aerospike Client for Rust as the Crate Of The Week.
Saw this the other day, tests for your README.
Hello! I saw this in my RSS reader today:
Sadly, for lack of nominations we have no Crate of this Week.
Therefore, I'd like to nominate trace-error for a crate of the week. In a nutshell, it exports
try!() macro replacements that thread error tracebacks behind the scenes. In author's words:
more lightweight and less macro-based alternative to error_chain
Hello. I've been working on a binary crate to generically decode protobuf messages:
I'd like to submit it for crate of the week consideration.
stdweb - A standard library for the client-side Web.
indicatif: "A rust library for indicating progress in command line applications to users."
I would like to nominate PX8. It is an Open Source Fantasy Console !
You can create tiny game in full Rust, or use Python/Lua. You have a built-in editor where you can modify your sprites.
You know that remove_dir_all function in std? Yeah, it basically doesn't work on windows, because files with open handles can't be deleted, and there are plenty of situations where this happens unexpectedly.
The remove_dir_all crate tries hard to really delete directories on windows. It is used now by the tempdir crate, and similar code is open-coded within rustup and rust-installer.