-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Improve support for ranges with nonstandard Integers #27302
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I agree, this seems a little strange. I understand why you need to remove this — and I agree it's a good thing to do, but I think we want to preserve the effective behavior here.
Perhaps we should detected (un)signed-ness based the behavior of
stop - start > zero(diff) && start - stop > zero(diff)
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's probably a good idea to code this up differently. I was going step by step through the logic and I think it's OK as it is, but it's not immediately obvious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the current implementation works (but is quite tough to read):
diff > zero(diff)
is always true for unsigned types at https://github.com/JuliaLang/julia/pull/27302/files#diff-c5053a63cd3df77d9079e95f29f350adR146 (since the casestop == start
is handled separately)(diff > zero(diff)) != (stop > start)
reduces tostop < start
(again,stop == start
is already handled), so far so good.remain = -convert(T, unsigned(-diff) % step)
.unsigned(-diff) === stop - start
.T
is an unsigned integer, so converting toT
is a no-op. Finally, the negation results in overflow (unlessunsigned(-diff) % step == 0
).last
is computed asstop - remain
, so (unlessremain == 0
) we're overflowing again and arriving at the correct answer.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh my that's extremely valuable. Can you insert that as a comment?