Urgau

@rustbot ready

> 2. This change would affect many tests and current codes, the checking of edition is just a temporary solution. Are there any better solutions? Does it manly just affect...

Only a small percentage of contributors read issues regularly enough to notice this issue. Our [Zulip > general](https://rust-lang.zulipchat.com/#narrow/stream/122651-general) channel, would be a better fit for this kind of inquiry.

I don't know if we should mention it in the diagnostic output it's already quite heavy; also mentioning the single column wouldn't be useful for the majority of users. However...

https://github.com/rust-lang/cargo/commit/3ca04e261e1abde062b1c58a31a0ae622547d972 from https://github.com/rust-lang/cargo/pull/12783 seems related. cc @weihanglo

I posted the draft for the announcement blog post: https://github.com/rust-lang/blog.rust-lang.org/pull/1313 It is targeting Rust 1.80 (nightly will branch in 8 days). It should be merged as soon as this PR...

While working on https://github.com/rust-lang/rust/pull/124209, I realised that with these documentation changes, Cargo would no longer have a canonical place for the feature. Which is perhaps a bit annoying, since in...

> This is still marked as a draft. Is it ready to go? @ehuss No, rust-lang/rust hasn't yet updated it's bootstrap compiler to beta 1.79, it's waiting https://github.com/rust-lang/rust/pull/124521.

I think if we try to merge before, we might get into weird behaviours, one I can think of is that bootstrap (the tool) unconditionnaly sets extra `--check-cfg` args, but...

In this case, with the CI passing, this PR is ready.