Skip to content

No labels!

There aren’t any labels for this repository quite yet.

S-types-tracked
S-types-tracked
Status: Being actively tracked by the types team
S-waiting-on-ACP
S-waiting-on-ACP
Status: PR has an ACP and is waiting for the ACP to complete.
S-waiting-on-author
S-waiting-on-author
Status: This is awaiting some action (such as code changes or more information) from the author.
S-waiting-on-bikeshed
S-waiting-on-bikeshed
Status: Awaiting a decision on trivial things.
S-waiting-on-bors
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
S-waiting-on-concerns
S-waiting-on-concerns
Status: Awaiting concerns to be addressed by the author
S-waiting-on-crater
S-waiting-on-crater
Status: Waiting on a crater run to be completed.
S-waiting-on-fcp
S-waiting-on-fcp
Status: PR is in FCP and is awaiting for FCP to complete.
S-waiting-on-LLVM
S-waiting-on-LLVM
Status: the compiler-dragon is eepy, can someone get it some tea?
S-waiting-on-MCP
S-waiting-on-MCP
Status: PR has a compiler MCP and is waiting for the compiler MCP to complete.
S-waiting-on-perf
S-waiting-on-perf
Status: Waiting on a perf run to be completed.
S-waiting-on-review
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
S-waiting-on-team
S-waiting-on-team
Status: Awaiting decision from the relevant subteam (see the T-<team> label).
stable-accepted
stable-accepted
Accepted for backporting to the compiler in the stable channel.
stable-nominated
stable-nominated
Nominated for backporting to the compiler in the stable channel.
subtree-sync
subtree-sync
PR updates a subtree (miri, clippy, etc). Ignored by no-merges check
T-bootstrap
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-cargo
T-cargo
Relevant to the cargo team, which will review and decide on the PR/issue.
T-community
T-community
T-compiler
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-core
T-core
Relevant to the core team, which will review and decide on the PR/issue.
T-crates-io
T-crates-io
Relevant to the crates.io team, which will review and decide on the PR/issue.
T-dev-tools
T-dev-tools
Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
T-docs-rs
T-docs-rs
Relevant to the docs-rs subteam, which will review and decide on the PR/issue.
T-infra
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
T-lang
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
T-lang-docs
T-lang-docs
Relevant to the lang-docs team.
T-libs
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
T-libs-api
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
T-opsem
T-opsem
Relevant to the opsem team