fix: numerical enum comparison #123
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, U# doesn't allow us to directly compare enum variable with number like: EnumHoge fuga = EnumHoge.Fuga; var comp = fuga >= 3; When EnumHoge.Fuga is 1, our expected result is comp=false, but the current implementation transcodes like: var comp = fuga != 3; which leads comp to be TRUE. Note that this phenomenon doesn't occur when you write enum in the comparison code like: var comp = HogeEnum.Fuga >= 3; because HogeEnum.Fuga is transcoded to const -1, which makes the >= operation int>=int. This change let you appropreately convert fuga >= 3 as it is.
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
yuta-game-music
changed the title
|
This will fix #68 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, U# doesn't allow us to directly compare enum variable with number like:
EnumHoge fuga = EnumHoge.Fuga;
var comp = fuga >= 3;
When EnumHoge.Fuga is 1, our expected result is comp=false, but the current implementation transcodes like: var comp = fuga != 3;
which leads comp to be TRUE.
Note that this phenomenon doesn't occur when you write enum in the comparison code like: var comp = HogeEnum.Fuga >= 3;
because HogeEnum.Fuga is transcoded to const 1, which makes the >= operation int>=int.
This change let you appropreately convert fuga >= 3 as it is.