-
Notifications
You must be signed in to change notification settings - Fork 785
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
Exhaustive pattern matches on numeric values yield compiler warning #6928
Comments
gdziadkiewicz
added a commit
to gdziadkiewicz/fsharp
that referenced
this issue
Aug 21, 2019
gdziadkiewicz
added a commit
to gdziadkiewicz/fsharp
that referenced
this issue
Aug 21, 2019
…ase requirement and add check for complete match similar to the one executed for bool.
gdziadkiewicz
added a commit
to gdziadkiewicz/fsharp
that referenced
this issue
Aug 24, 2019
…d added check for complete match.
gdziadkiewicz
added a commit
to gdziadkiewicz/fsharp
that referenced
this issue
Aug 24, 2019
…d added check for complete match.
gdziadkiewicz
added a commit
to gdziadkiewicz/fsharp
that referenced
this issue
Aug 25, 2019
cartermp
pushed a commit
that referenced
this issue
Aug 29, 2019
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this issue
Feb 23, 2021
…d added check for complete match. (dotnet#7445) * dotnet#6928 - Removed SByte and Byte from default case requirement and added check for complete match. * Upgrade new tests (dotnet#6928)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created a function to compute the AES S-Box. This is its code:
However, the compiler raises an "Incomplete pattern matches on this expression" warning, even though my code handles all 256 possible cases for the
byte
type.Repro steps
Already covered.
Expected behavior
Code compiles successfuly without warnings.
Actual behavior
Known workarounds
Have a redundant wildcard case at the end of
match
statement.The text was updated successfully, but these errors were encountered: