I nominate this abuse of the type system:
Thank you @taiki-e!
Thus, it aims for:
- simplicity: define a set of SQL statements. Just add more SQL statement to change the schema. No external CLI, no macro.
performance: no need to add a table to be parsed, the
user_versionfield is at a fixed offset in the sqlite file format.
This is a unix utility for letting you split stdout from a command in a GUI, then get the results back in the terminal to be passed along. It's meant to let you explore command output as a table.
qcell been nominated yet? It's a heavily underrated crate, particularly when working with dynamic views of trait objects (runtime polymorphism).
A neat toolbox for manipulating tuples. New and still underappreciated crate with just one star on github. I used it recently in tandem with derive_new to handle the tuples that diesel returns on joins. I just wanted to add another item to the tuple (
append) before I fed the elements into the new-method (
apply) for my return-struct. Very nice!
I'd like to nominate a crate that my friend has spent much time on: a fast no_std websocket crate called 'embedded-websocket'
I would like to nominate cargo guppy, a crate which can be used to track and query Cargo dependency graphs.
The crate is very well documented, tested and serves, in my opinion, as a great example on how to structure and write beautiful Rust API's.
Still not seen a cargo dependency tree viewer in 3D yet. There's surely lots of fun to be had there.
(Bonus points for cyberpunk theming)
Hi everyone! I'd like to make a self-suggestion: GitHub - mikaelmello/inquire: A Rust library for building interactive prompts
It is a crate to build interactive prompts that was inspired by the amazing (IMO) Github CLI app. You might be familiar with a similar crate that is dialoguer. To make mine stand out, I focused a lot on providing the greatest developer experience possible with nice to use APIs, sane defaults and an extensive documentation, besides more features
I talked about it on the last RustConf and people loved it! Thought it might be worth a shot to put it here too, thanks!
I'd like to recommend ulid crate for making "Universally Unique Lexicographically Sorted Identifiers."
I'd like to nominate arbitrary, a crate for state-of-the-art fuzzing and property-based testing:
This crate doesn't include a proptestering or fuzzing "runner", it only defines a trait to generate arbitrary values. The trait is simple, but very powerful -- it allows you to get minimization and coverage-based search for structured input for free.
A promising crate, for those who work with both Rust and TypeScript ts-rs : auto-generate your TypeScript definitions directly from your Rust structs, with many customization options
Big up to its author and contributors
bigdecimal or please suggest if you know something better
Thats really useful. Would like to try it out asap.
I would like to nominate Flowistry, which is a static analysis tool for Rust. It's implemented as a VSCode plugin and looks really awesome!
This crate provides extension methods on all types that allow transparent, temporary, inspection/mutation (tapping), transformation (piping), or type conversion. These methods make it convenient for you to insert debugging or modification points into an expression without requiring you to change any other portions of your code.
I'd like to nominate miette, a new crate for error handling and reporting that's a mixture of thiserror, anyhow/eyre, and codespan-reporting, all in a nice neat package. It adds stuff like unique error codes (with automatic linking to docs-rs), help messages, footers, multiple messages, and even snippets.
I just tagged 3.0.0 and I'd love to get some more attention on it!
Here's what an example error looks like:
I was thinking maybe this tiny crate might be interesting.
skip_error allows you to discard a
Result::Err and continue to the next iteration of the loop. Usually, we would think short-circuit is a good idea, but in some cases, you might want to continue the processing and just ignore the error. On top of that,
skip_error can log the error for you, so the
Err does not vanish into the ether (support for
tracing). I'd be happy to see if there is any interest for such a small utility.
(full disclosure: I'm one of the main maintainer of the crate)