Skip to content

Issues: rust-lang/rust

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
8 Open 91 Closed
8 Open 91 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Compilation error when matching reference to empty enum A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-patterns Relating to patterns and pattern matching C-bug Category: This is a bug. F-exhaustive_patterns `#![feature(exhaustive_patterns)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team T-types Relevant to the types team, which will review and decide on the PR/issue.
#131452 opened Oct 9, 2024 by dhedey
@Nadrieril
26
Tracking Issue for Never Patterns (never_patterns) A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns B-experimental Blocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize). B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-never_patterns `#![feature(never_patterns)]` S-tracking-impl-incomplete Status: The implementation is incomplete. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#118155 opened Nov 22, 2023 by Nadrieril
5 tasks
42
Rust match bound non-exhaustive patterns when all possible patterns for char are handled A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-patterns Relating to patterns and pattern matching C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#108932 opened Mar 9, 2023 by Arthurdw
1
mutually exclusive match arms with if cases are not recognized to be covering A-diagnostics Area: Messages for errors, warnings, and lints A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns C-enhancement Category: An issue proposing an enhancement or a PR with one. D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#93611 opened Feb 3, 2022 by drahnr
6
Tracking Issue for #![feature(non_exhaustive_omitted_patterns_lint)] A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-non_exhaustive_omitted_patterns_lint `#![feature(non_exhaustive_omitted_patterns_lint)]` S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR T-lang Relevant to the language team, which will review and decide on the PR/issue.
#89554 opened Oct 5, 2021 by Nadrieril
11 of 15 tasks
21
Extend overlapping ranges lint to cover cases with more than a single element overlapping A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. I-needs-decision Issue: In need of a decision. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#65477 opened Oct 16, 2019 by estebank
12
Arms permitted when matching on uninhabited types A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#55123 opened Oct 16, 2018 by varkor
8
Tracking issue for RFC 1872: exhaustive_patterns feature A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-patterns Relating to patterns and pattern matching B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-exhaustive_patterns `#![feature(exhaustive_patterns)]` S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#51085 opened May 26, 2018 by kennytm
2 of 3 tasks
33
ProTip! no:milestone will show everything without a milestone.