Skip to content

'non-exhaustive match failure' in fold_ty (inner constraint) #970

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

Jump to bottom
Closed
jruderman opened this issue Sep 24, 2011 · 0 comments
Closed

'non-exhaustive match failure' in fold_ty (inner constraint) #970

jruderman opened this issue Sep 24, 2011 · 0 comments

Comments

@jruderman
Copy link
Contributor 

tag maybe_ordered_pair {
    yes({low: int, high: int} : less_than(*.low, *.high));
    no;
}
pure fn less_than(x: int, y: int) -> bool { ret x < y; }
fn main() { }

upcall fail 'non-exhaustive match failure', ../src/comp/middle/ty.rs:671

I guess the alt in fold_ty is missing ty_constr
@ghost ghost assigned catamorphism Sep 25, 2011
@jruderman jruderman mentioned this issue Mar 15, 2012
Closed
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@bjorn3
Sync fn_sig_for_fn_abi with upstream for generator resume args
eab4c90 
Fixes rust-lang#970
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@wsmoses
Handle compiler.used (rust-lang#970)
ae31fac
coastalwhite pushed a commit to coastalwhite/rust that referenced this issue Aug 5, 2023
@tmiasko
Use a bootstrap guard for modules with new target features (rust-lang…
f1ed228 
…#970)

The recently added modules use target features that are not yet
available in rustc compiler used for bootstrapping.

Guard them with `#[cfg(not(bootstrap))]`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@catamorphism @jruderman