Skip to content

De-abuse TyKind::Error in exhaustiveness checking #71930

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

Merged
merged 18 commits into from
May 21, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/librustc_mir_build/hair/pattern/_match.rs
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,9 @@
/// (`Constructor`, `Fields`) pairs, handling all the special cases correctly.
///
/// Caveat: this constructors/fields distinction doesn't quite cover every Rust value. For example
/// a value of type `Rc<u64>` doesn't fit this idea very well, nor do function pointers and various
/// other things. However, the idea covers everything that can be pattern-matched, and this is all
/// we need for exhaustiveness checking.
/// a value of type `Rc<u64>` doesn't fit this idea very well, nor do various other things.
/// However, this idea covers everything that can be pattern-matched, and this is all we need for
/// exhaustiveness checking.
///
///
/// # Algorithm
Expand Down