Tracking Issue for `cfg_version`

[epage]

Summary

RFC: #2523
Original issue: N/A
Implementation:

• Initial implementation
  Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#cfg-version

Allow dependencies conditioned on the Rust version in a way that matches with #[cfg(version)]

[target.'cfg(not(version(1.70.0))`.dependencies]
is-terminal = "0.4.2"

See also

• Tracking issue for RFC 2523, #[cfg(version(..))] rust#64796
• rustc stabilization: Stabilize #[cfg(version(...))] rust#141137
• https://github.com/rust-lang/rfcs/blob/master/text/2523-cfg-path-version.md

Unresolved Issues

No response

Future Extensions

No response

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

[epage]

CC @mo8it

[madsmtm]

Note: depending on the decided syntax, this might actually end up being (with quotes):

[target.'cfg(not(version("1.70.0"))`.dependencies]
is-terminal = "0.4.2"

(Just noting so that we don't accidentally stabilize one syntax in the language, and another in Cargo).