Skip to content

Labels

Labels

  • Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself.
  • Diagnostics: An error or lint that should account for edition differences.
  • Diagnostics: spans don't point to exactly the erroneous code
  • Diagnostics: Inconsistency in formatting, grammar or style between diagnostic messages.
  • Diagnostics: A diagnostic that is giving misleading or incorrect information.
  • Diagnostics: A structured suggestion resulting in incorrect code.
  • Diagnostics: Adding a (structured) suggestion would increase the quality of the diagnostic.
  • Diagnostics: Confusing error or lint; hard to understand for new users.
  • Diagnostics: An error or lint that needs small tweaks.
  • Diagnostics: An error or lint that doesn't give enough information about the problem at hand.
  • Diagnostics: Diagnostics that are unaware of Unicode and trigger codepoint boundary assertions
  • Diagnostics: Too much output caused by a single piece of incorrect code.
  • This PR / issue is in PFCP or FCP with a disposition to close it.
  • This issue / PR is in PFCP or FCP with a disposition to merge it.
  • This issue / PR is in PFCP or FCP with a disposition to postpone it.
  • Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
  • Call for participation: Hard difficulty. Experience needed to fix: A lot.
  • Call for participation: Help is requested to fix this issue.
  • Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
  • Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
  • Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
  • This issue needs exploration and design to see how and if we can fix/implement it
  • Call for partcipation: This issues needs some investigation to determine current status
  • Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
  • Call for participation: This issue needs a stacktrace.
  • Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
  • Call for participation: An issue involves lots of work and is better handled as many small tasks.
  • `#![feature(abi_c_cmse_nonsecure_call)]`
  • `#![feature(abi_ptx)]`
Labels Index · GitHub