-
Notifications
You must be signed in to change notification settings - Fork 21
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
F*: pattern matching is disallowed on usize
s, isize
s (+u128
/i128
/f32
/f64
)
#464
Labels
Comments
W95Psp
changed the title
F*: pattern matching is disallowed on
F*: pattern matching is disallowed on Apr 11, 2024
usize
susize
s, isize
s (+u128
/i128
)
W95Psp
added a commit
that referenced
this issue
Apr 11, 2024
This was referenced Apr 11, 2024
|
W95Psp
added a commit
that referenced
this issue
Apr 11, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 15, 2024
fix(engine/f*): better error for #464
6 tasks
There's a design in #806 that needs to get implemented. |
5 tasks
W95Psp
added
the
marked-unimplemented
Issue refered by `Unimplemented {issue_id...}` in the engine
label
Oct 2, 2024
W95Psp
changed the title
F*: pattern matching is disallowed on
F*: pattern matching is disallowed on Oct 31, 2024
usize
s, isize
s (+u128
/i128
)usize
s, isize
s (+u128
/i128
/f32
/f64
)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently we do not support matching on
usize
in the F* backend.This is because of our encoding of
usize
: a usize is defined as an opaque type being maybe au16
, au32
, or maybe au64
. This encoding is important since the size ofusize
s varies according to the architecture being targetted.Solutions:
usize
as ax: u64 {range (v x) u16_inttype \/ range (v x) u32_inttype \/ range (v x) u64_inttype}
(wdyt about this @karthikbhargavan?)The text was updated successfully, but these errors were encountered: