Skip to content

exhaustiveness checking sometimes fails to detect missing variants #3011

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.

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

Closed
nikomatsakis opened this issue Jul 25, 2012 · 1 comment
Closed
Labels
A-type-system Area: Type system

Comments

@nikomatsakis
Copy link
Contributor

I can't get a narrow test case, but the function bound_region_to_str() was missing a variant and no error was reported. The relevant case is now handled, but I added a FIXME tagged with this issue # so if you want to debug it, you can remove that variant.

@nikomatsakis
Copy link
Contributor Author

never mind, turned out to be user error, but of a scary kind

bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
RalfJung pushed a commit to RalfJung/rust that referenced this issue Aug 6, 2023
A bit of spell-checking

I noticed the one error in miri-script and took care of a few more shallow ones.
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Update Rust toolchain from nightly-2024-01-24 to nightly-2024-01-25
without any other source changes.
This is an automatically generated pull request. If any of the CI checks
fail, manual intervention is required. In such a case, review the
changes at https://github.com/rust-lang/rust from
rust-lang@5d3d347
up to
rust-lang@7ffc697.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-type-system Area: Type system
Projects
None yet
Development

No branches or pull requests

1 participant