A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness

Area: Custom and system allocators

A-associated-items

Area: Associated items such as associated types and consts.

Area: Async & Await

Area: #[attributes(..)]

A-borrow-checker

Area: The borrow checker

Area: build system

Area: `do catch { .. }` expressions

Area: closures (`|args| { .. }`)

Area: Code generation

Area: implicit and explicit `expr as Type` coercions

Area: std::collections.

Area: Concurrency related issues.

Area: constant evaluation (mir interpretation)

Area: const fn foo(..) {..}. Pure functions which can be applied at compile time.

Area: Cross compilation

Area: Debugging information at runtime in generated code.

Area: destructors (Drop, ..)

Area: Error messages

Area: Documentation tests, run by rustdoc

Area: rustc_driver that ties everything together into the `rustc` compiler

Area: Dynamically Sized Types

A-edition-2018-lints

Area: lints supporting the 2018 edition

Area: Foreign Function Interface (FFI)

Area: frontend (errors, parsing and HIR)

Area: Generators

Area: The grammar of Rust

Area: the High level Intermediate Representation (HIR)

Area: impl Trait. Universally / existentially quantified anonymous types with static dispatch.

Area: Incremental compilation

Area: Type inference

A-inline-assembly

Area: inline asm!(..)

A-intra-doc-links

Area: Intra-doc links, the ability to link to items in docs by name

Area: Iterators

Area: #[test] related

Area: lifetime related

Area: linking into static, shared libraries and binaries

Area: Lints (warnings about flaws in source code) such as unused_mut.

Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

Issues which affect macros 1.2

Area: declarative macros 2.0, https://github.com/rust-lang/rust/issues/39412

Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)

Area: crate metadata

Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html

Area: #[naked], prologue and epilogue-free, functions, https://git.io/vAzzS

Area: Non Lexical Lifetimes (NLL)

A-parallel-queries

Area: Parallel query execution

Area: The parsering of rust source code to AST.

Area: compiler plugins, doc.rust-lang.org/nightly/unstable-book/language-features/plugin.html

Area: Pretty printing.

Area: Path resolution

Area: Rust Language Server (RLS)

Area: The runtime of Rust or using Rust to implement a runtime.

A-rust-2018-preview

Area: The 2018 edition preview

Area: The rustbuild system (x.py)

Area: Sanitizers for correctness and code quality.

A-save-analysis

Area: saving results of analyses such as inference and borrowck results to a file.

Area: Security related issues (example: adress space layout randomization)

Area: SIMD (Single Input Multiple Data)

A-slice-patterns

Area: slice patterns, https://github.com/rust-lang/rust/issues/23121

A-specialization

Area: Trait impl specialization

Area: Spurious failures in builds (spuriously == for no apparent reason)

Area: issues related to #[stable] and #[unstable] attributes themselves.

A-suggestion-diagnostics

Area: suggestions generated by the compiler appplied by cargo fix

Area: Syntax extensions

A-synthetic-impls

Area: Synthetic impls, used by rustdoc to document auto traits and traits with blanket impls

Area: compile-target specifications

Area: The testsuite used to check the correctness of rustc

A-thread-locals

Area: Thread local storage (TLS)

Area: Trait system

Area: The type system

Area: unicode related

Area: visibility modifiers such as `pub`

Approved by a merged RFC but not yet implemented.

B-RFC-implemented

Approved by a merged RFC and implemented.

Implemented in the nightly compiler and unstable.

Accepted for backporting to the compiler in the beta channel.

Nominated for backporting to the compiler in the beta channel.

Category: This is a bug.

Category: PRs that clean code up or issues documenting cleanup.

Category: A PR with an enhancement or a proposed on in an issue.

C-feature-accepted

Category: A feature request that has been accepted pending implementation.

C-feature-request

Category: A feature request, i.e: not implemented / a PR.

C-future-compatibility

Category: future compatibility lints

C-tracking-issue

Category: A tracking issue for something unstable.

chalk-integration

Issues blocking "preliminary chalk integration" milestone

disposition-close

This PR / issue is in PFCP or FCP with a disposition to close it.

disposition-merge

This issue / PR is in PFCP or FCP with a disposition to merge it.

disposition-postpone

Call for participation: Experience needed to fix: Easy / not much

Call for participation: Experience needed to fix: Hard / a lot

Call for participation: Help is requested / needed by the one who filed the issue to fix it.

Call for participation: Experience needed to fix: Medium / intermediate

Call for participation: This issue is currently mentored.

E-needs-bisection

Call for participation: This issue needs a bisection to find the exact PR causing the regression

Call for participation: This issue is in need of a mentor.

Call for participation: writing correctness tests

final-comment-period

In the final comment period and will be merged soon unless new substantive objections are raised.

finished-final-comment-period

The final comment period is finished for this PR / Issue.

hacktoberfest projects - https://hacktoberfest.digitalocean.com/

Problems and improvements with respect to memory usage during compilation.

Problems and improvements with respect to compile times.

Compiler crashes, use I-ICE instead when rustc panics with a message saying it is an ICE.

Compiler never terminates, resulting from infinite loops, deadlock, livelock, etc.

Problems and improvements with respect to binary size of generated code.

Describes an Internal Compilation Error (ICE) or ❄️- a panic bug in the compiler.

I-needs-decision

Issues in need of decision.

Indicates that an issue has been nominated for prioritizing at the next team triage meeting.

Problems and improvements with respect to performance of generated code.

The issue is invalid and has been raised in error.

Issues about issues themselves ("bugs about bugs")

This change is insta-stable, so needs a completed FCP to proceed.

This change is large or controvercial enough that it should have an (e-)RFC accepted before doing it

Working towards the "valid code works" goal

NLL-diagnostics

Working torwads the "diagnostic parity" goal

NLL-fixed-by-NLL

Bugs fixed, but only when NLL is enabled.

Working towards the "performance is good" goal

Issues related for using Polonius in the borrow checker

Reference material for NLL

Working towards the "invalid code does not compile" goal

Operating system: Android

Target: ARM processors

Target: asm.js - http://asmjs.org/

Operating system: DragonFly BSD

Operating system: FreeBSD

Operating system: Fuchsia

Operating system: GuixSD - https://www.gnu.org/software/guix/

Operating system: Apple's iOS.

Operating system: Linux

Operating system: macOS

Target: MIPS processors

Target: The musl libc

Operating system: NetBSD

Operating system: NixOS, https://nixos.org/

Target: the NVPTX LLVM backend for running rust on GPUs, https://llvm.org/docs/NVPTXUsage.html

Operating system: OpenBSD

Target: PowerPC processors

Operating system: Redox, https://www.redox-os.org/

Target: RISC-V architecture

Operating system: Solaris

Target: SPARC processors

Target: SystemZ processors (s390x)

Target: WASM (WebAssembly), http://webassembly.org/

Toolchain: GNU, Operating system: Windows

Toolchain: MSVC, Operating system: Windows

Operating system: Windows

Target: x86 processors

Target: x64 processors

Medium priority

proposed-final-comment-period

Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.

regression-from-stable-to-beta

Performance or correctness regression from stable to beta.

regression-from-stable-to-nightly

Performance or correctness regression from stable to nightly.

regression-from-stable-to-stable

Performance or correctness regression from one stable version to another.

Marks issues that should be documented in the release notes of the next release.

rust-2-breakage-wishlist

In the wishlist of breaking changes that requires rust 2.0

S-blocked-closed

Status: marked as blocked ❌ and closed because resolving the block is expected to take a long time.

Status: marked as blocked ❌ on something else such as an RFC or other implementation work.

S-inactive-closed

Status: closed due to inactivity.

S-waiting-on-author

Status: The marked PR is awaiting some action (such as code changes) from the PR author.

S-waiting-on-bikeshed

Status: Awaiting a decision on trivial things.

S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

S-waiting-on-crater

Status: Waiting on a crater run to be completed.

S-waiting-on-perf

Status: Waiting on a perf run to be completed.

S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

S-waiting-on-team

Status: Awaiting decision from the relevant subteam (see the T-<team> label).

stable-accepted

Accepted for backporting to the compiler in the stable channel.

stable-nominated

Nominated for backporting to the compiler in the stable channel.

Relevant to the cargo subteam, which will review and decide on the PR/issue.

Relevant to the compiler subteam, which will review and decide on the PR/issue.

Relevant to the core team, which will review and decide on the PR/issue.

Relevant to the dev-tools subteam, which will review and decide on the PR/issue.

Relevant to the documentation subteam, which will review and decide on the PR/issue.

Relevant to the IDEs and editors team, which will review and decide on the PR/issue.

Relevant to the infrastructure subteam, which will review and decide on the PR/issue.

Relevant to the language subteam, which will review and decide on the PR/issue.

Relevant to the libraries subteam, which will review and decide on the PR/issue.

Relevant to the release subteam, which will review and decide on the PR/issue.

Relevant to the rustdoc subteam, which will review and decide on the PR/issue.

Working Group: Codegen (Runtime perf and code size)

WG-compiler-errors

Working group: compiler errors

WG-compiler-front

Working group: front end (Parser, HIR)

WG-compiler-incr

Working group: incremental compilation

WG-compiler-middle

Working group: Middle end; Everything between frontend (parser, HIR) and backend (trans, llvm)

WG-compiler-performance

Working group: Compiler Performance

WG-compiler-traits

Working group: Traits, https://internals.rust-lang.org/t/announcing-traits-working-group/6804

Compiler/language requests of the embedded Working Group

Working group: Epoch (2018) management

No labels found. Sorry about that.