Thanks, works great: I've given this the testing treatment our RIOT OS build system is getting (which is not a full build-all test but usually representative enough), and all works fine. I'd love to update the docs to install the latest released version rather than an untagged git commit.

Is there anything that can be done to advance this to a crates.io release?

Is there anything that can be done to advance this to a crates.io release?

We hit some snags on that, because there's a cargo bug where the workspace Cargo.lock is not considered when publishing. It's fixed in the next cargo version, but of course we're pinned, so we'd need to update that. Or it might be possible to publish with a Cargo.lock that doesn't work on the pinned nightly, as everything published is fine on stable (would this cause anyone problems?).

Is the GitHub release (with its tagged commit) enough for now? We're trying to publish the rest of the crates (most of the smaller dependency ones have been already), we've just been busy with other stuff, and will try to get it done soon.

My impression on this is that anyone who uses the crate through crates.io will not get the nightly-version pinning anyway, but whatever they have installed. People might in theory install it through cargo +nightly-2022-... install c2rust, but they can not reliably find out which nightly they should use without cloning the repository in the first place (it's not discoverable through the released version AFAICT), and when they've cloned it, they don't even have to look it up any more but can just install from the checkout that has both the right Cargo.lock and the rust-toolchain file.