Write safer FFI code in Rust without polluting it with unsafe code
is a disk space navigator for the terminal (written in Rust, of course ). (full disclosure: I am the author)
k9 - Rust Testing Library
A program that simulates the behavior of bodies that attract each other in real-time using wgpu.
Async DoubleCheckedCell helps avoid race conditions when a program needs to initialize data asynchronously and lazily.
SuckIT allows you to recursively visit and download a website's content to your disk.
Much faster than tools like HTTrack.
stdext is a crate with minor additional features for
std. It is designed to be more agile in terms of getting a new
std feature to your codebase, and less strict in terms of added features.
assert_equal macro looks very useful. Checking the difference between structs is indeed painful with the standard
I nominate nnnoiseless, a port of Xiph's RNNoise (written in C) to safe Rust. The release was accompanied by a blog post by the author, where they explain some of the porting process as well as subsequent performance optimizations that lead to the port overtaking the original C version in their benchmark. There has been a discussion on the subreddit.
Another audio related blog post:
pre - Helper for compile-time checking some aspects of unsafe functions.
sophia a Rust toolkit for RDF and Linked Data.
deltoid, a library for working with delta's.
I'd like to nominate neli, a crate for working with Linux Netlink sockets in a type-safe way, including rtnetlink for network configuration.
I nominate bevy, a game engine that was released yesterday after having been in development for six months by a single person. The website and documentation look really good.