-
Notifications
You must be signed in to change notification settings - Fork 215
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
feat: use more efficient field merger code #6815
Draft
TomAFrench
wants to merge
4
commits into
master
Choose a base branch
from
tf/explore-re-adding-value-merger-change
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c86f962
feat: use more efficient field merger code
TomAFrench 16ba340
.
TomAFrench bab687e
Merge branch 'master' into tf/explore-re-adding-value-merger-change
TomAFrench 5570a8b
Merge branch 'master' into tf/explore-re-adding-value-merger-change
TomAFrench 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
Oops, something went wrong.
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.
Related to this I found that when we were casting to
Field
we saved a lot of range constraints implied on the binary operations performed onUnsigned
types. First I thought that must be unsafe as it would mask a potential overflow, but with thec*a + !c*b
formula below it seems safe (or actually it has anelse_condition
below, but assuming that they are mutually exclusive).I assume you're not doing the
c * (a-b) + b
trick because of a potential overflow, but isn't it true that mathematically this should be okay, if the cost of the extraCast
s toField
would be acceptable?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, we're not concerned about overflows here as the merged value is constrained to
then_value
orelse_value
and any underflow in the difference term will disappear (This is why we needed to cast to Fields as the integer types imply checked arithmetic)I did this just for fields in this PR as this doesn't need the inputs to be casted to fields and back (as it's already the correct type).