rust-lang / rust-lang/rust

Tracking Issue for `cfg_os_version_min`

Open
#136,866 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue T-compiler T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the RFC "cfg_os_version_min" (rust-lang/rfcs#3750).
The feature gate for the issue is #![feature(cfg_os_version_min)].
The unstable documentation for this can be found here.

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved Questions

TODO once the RFC is accepted: list all the "unresolved questions" found in the RFC

Implementation history

@rustbot label t-compiler t-lang

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RFC 3750 and review the implementation history in rust-lang/rust pull requests 136867 and 136868. Use the tracking checklist to identify remaining platform, documentation, style-guide, and stabilization work. Done means the RFC is implemented across the supported targets and the remaining checklist items are completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.