Kornel

I think users should be encouraged to specify cargo-readable MSRV when it lands: https://github.com/rust-lang/rust/issues/65262 Once this is used in Cargo to resolve dependencies (and it's doable even without Cargo's support...

I think there's a value in specifying MSRV in Cargo.toml as a warning to users of old compiler — such explicit error is much better than a compilation error that...

It doesn't address this problem. There is still going to be a delay between `cargo publish` and the crate being available globally. It would be nice to improve this, but...

I'd especially like this to work on command line. `--no-default-features` is lengthy, and requires user to repeat other defaults. A syntax sugar for it would be very helpful. Here's a...

It seems to be related, but a bit backwards, to temp vs non-temp separation of directories proposed in #6227

@dpaoliello I've imagined this done in reverse: keep the final build artifacts that people care about in the target dir where they are, but start moving everything else (temp files,...

I think this feature is salvageable. It's a matter of yanking a few popular crates that have too lax dependencies. I've started a crusade against `"*"` deps:

@untitaker There's nothing to worry about yanking of old broken crates. It helps users of both new and old Rust versions. First of all, the crates that need to be...

Yanking doesn't delete crates, only hides them. Users who used yanked crates can continue to use them, because crate versions locked in lockfiles are usable indefinitely, even if they're yanked.

Users of old Rust who don't have a lockfile are unable to use crates.io any more. At all.