cross VS kondo

The -musl targets for Linux make it easy to dodge the need to compile against the oldest glibc you want to support if your project is pure Rust and cross is a Docker wrapper which aims to make cross-targeting in other scenarios as easy as with Go.)

...though, funny enough, if you have enough experience with Rust to not get bogged down in the details and you use cross to work around Rust's "take your time but get it right" approach to cross-building, Rust is often better at little CLI tools, purely because of how valuable it is to be able to teach the type system to check so many invariants at compile time.

Another thing to keep in mind for if just using the musl target with your usual setup is insufficient (eg. if you need to use a crate like ttspico which statically links some C code) is cross, which makes it really easy to use Docker to build and run tests.

You can use cargo sweep or kondo to clean up unused files.

I like to use kondo for that

Blast em https://github.com/tbillington/kondo

Sorry for spoiling your fun, but did you give kondo a try?

This is cool :) I'll have to poke around how you did Async, I've been dragging my feet on implementing it in kondo.