Rollup merge of #163399 - Kixunil:cfg_version_in_doc_cfg, r=fmease
Support `cfg_version` in `doc_cfg`
The (unstable) `cfg_version` feature allows one to enable features conditioned on th Rust version and `doc_cfg` makes `rustdoc` show nice documentation of feature flags. Despite these being unstable, `doc_cfg` is widely used in docs.rs and crates often turn on the feature. While it may seem pointless to support `cfg_version` since it's unstable and nobody is really using it, there are two reasons why it in fact does make sense. First, it's a step towards making both features more complete, so it's a step towards stabilization. Second, many crates currently use other ways (build scripts) to achieve the same thing as `cfg_version`. However these could still take advantage of the `doc_cfg` feature, especially on docs.rs by pretending that they do use `version` adding the attribute `#[cfg_attr(docsrs, doc(cfg(version = "1.81.0")))]`
This commit adds a very simple support for the attribute: it translates it to "Rust version at least {}", which reads better than `version=`. As was already discussed, the word "version" is too ambiguous, so saying "Rust version" is more clear. Also while the `=` sign is considered by some to be understandable in `cfg`, it is arguably harder to read in doc, so saying "at least" is less confusing.
Cc rust-lang/rust#64796 rust-lang/rust#43781
Screenshot of how the change looks in doc:
<img width="960" height="63" alt="Screenshot of rustdoc output after the change" src="https://github.com/user-attachments/assets/1981ed30-2314-463d-bc8c-e7ae2ac86c84" />
Website | Getting started | Learn | Documentation | Contributing
This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.
Performance: Fast and memory-efficient, suitable for critical services, embedded devices, and easily integrated with other languages.
Reliability: Our rich type system and ownership model ensure memory and thread safety, reducing bugs at compile-time.
Productivity: Comprehensive documentation, a compiler committed to providing great diagnostics, and advanced tooling including package manager and build tool (Cargo), auto-formatter (rustfmt), linter (Clippy) and editor support (rust-analyzer).
Read “Installation” from The Book.
If you really want to install from source (though this is not recommended), see INSTALL.md.
See https://www.rust-lang.org/community for a list of chat platforms and forums.
See CONTRIBUTING.md.
For a detailed explanation of the compiler's architecture and how to begin contributing, see the rustc-dev-guide.
Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.
See LICENSE-APACHE, LICENSE-MIT, and COPYRIGHT for details.
The Rust Foundation owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”).
If you want to use these names or brands, please read the Rust language trademark policy.
Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.