Support universal equality of unsigned numeric types #3584
Merged
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
…piler plugin. Use BoxesRunTime.equals methods instead of `_Object.__scala_==`
- Fix CI for usize on linux-x86 - Fix compilation warning
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.
This change allows to use universal equality for combination of signed and unsigned numeric types. It means we can run comparisons like
2 + 2 == 4.toUInt, or-1.toUByte == 255.To allow for that when used in erased context, we modify the NIR generated for
==and!=primitives. These now would delegate toscala.runtime.BoxesRunTime.equalsinstead of delegating to customObject.__scala_==which now becomes obsolete and removed.All numeric equality comparsions are now available between any of
Byte,Short,Int,Long,UByte,UShort,UInt,UByte,Size,USizeandChar.