Aloso

What’s the bad scenario you’re worried about here? What type of data you’re specifically worried about? Do you expect me to maliciously manipulate the data, or is even well-intentioned curation and use of heuristics somehow not acceptable?

I think they are worried that some crates may not show up in the search results, either because their author requested their removal, or you decreased their search ranking for political reasons.

And I agree with you that crates.io is not a viable alternative due to the poor quality of the search results. So switching from lib.rs to crates.io doesn't make sense for this reason alone, since crates.io may not display the crate you're looking for either, unless you already know its name.

You need to tell the user that this is an error, otherwise they don't know if it succeeded or not.

error: --att cannot be used at the same time as --intel

The last line is incomprehensible, just use a full sentence.

There are executors for more specific use cases.

• For example, bastion is a "Highly-available Distributed Fault-tolerant Runtime", inspired by Erlang, and including an async executor.
• embassy includes an async executor specifically for embedded systems.
• fuchsia-async is an executor for use in the Fuchsia OS.
• wasm-bindgen-futures converts Rust Futures to JavaScript Promises and schedules them to run to completion. It could also be seen as a (very basic) executor.

I think that's just the number of subs that announced they will go dark.

Are you sure you're on the latest version (0.0.33)? Maybe it wasn't updated yet. You can go to the play store and check.