BetaGive feedback
Issues
Search results
Should public_private_dependencies consider unreachable visibility?
Category: This is a bug.Category: This is a bug.feature: public_private_dependenciesfeature: public_private_dependenciesLint: public_private_dependenciesLint: public_private_dependenciesRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#130079 In rust-lang/rust;#[repr()]
is allowed where it shouldn'tArea: Attributes (`#[…]`, `#![…]`)Area: Attributes (`#[…]`, `#![…]`)Category: This is a bug.Category: This is a bug.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#129606 In rust-lang/rust;Decide whether we want MSRV-gating
Category: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#129445 In rust-lang/rust;Refining generic bounds in trait method
Area: Trait systemArea: Trait systemCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Status: Open.#129251 In rust-lang/rust;Inconsistency between tuples and struct-tuples with
min-exhaustive-patterns
Area: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.`#![feature(min_exhaustive_patterns)]``#![feature(min_exhaustive_patterns)]`Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#129043 In rust-lang/rust;Language vs. implementation threat models and implications for TypeId collision resistance
Category: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.Nominated for discussion during a lang team meeting.Nominated for discussion during a lang team meeting.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#129030 In rust-lang/rust;Incremental compilation relies on hashes for soundness
Area: Incremental compilationArea: Incremental compilationCategory: This is a bug.Category: This is a bug.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#129016 In rust-lang/rust;optimize
attribute applied to things other than methods/functions/c…Nominated for discussion during a lang team meeting.Nominated for discussion during a lang team meeting.Status: Awaiting decision from the relevant subteam (see the T-<team> label).Status: Awaiting decision from the relevant subteam (see the T-<team> label).Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open (in progress).rust-lang/rustnumber 128943#128943 In rust-lang/rust;Need an explicit part for requirements which can not be checked by compiler in trait docs
Area: documentation for any part of the project, including the compiler, standard library, and toolsArea: documentation for any part of the project, including the compiler, standard library, and toolsCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.Status: Open.#128926 In rust-lang/rust;"impl Copy" can bypass field privacy
Area: Trait systemArea: Trait systemArea: Visibility / privacyArea: Visibility / privacyRelevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Status: Open.#128872 In rust-lang/rust;irrefutable_let_patterns
should not lint at the start of anelse if
let-chainArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.Category: This is a bug.Category: This is a bug.`#![feature(let_chains)]``#![feature(let_chains)]`Lint: irrefutable_let_patternsLint: irrefutable_let_patternsRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Status: Open.#128661 In rust-lang/rust;Trait method shadowing can make adding a method to a sealed trait a breaking change and silently change behaviour in downstream crates
Category: This is a bug.Category: This is a bug.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.Status: Open.#128509 In rust-lang/rust;