ABI: Do not add extra constraints for symbolic arguments #875
Conversation
This file contains hidden or 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
The extra constraints are not necessary because the proper range should be enforced directly in the bytecode. Moreover, the constraints added by `inRangeSigned` were equivalent to True anyway.
blishko
force-pushed
the
cleanup-symbolic-abi
branch
2 times, most recently
from
c19c9d4 to
078f2ca
Compare
Collaborator
|
Are these constraints always enforced in the bytcode or just in the code produced by solc? |
Collaborator
Author
|
They should be enforced by solc, because these types are solc constructs. |
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.
Description
The extra constraints are not necessary because the proper range should be enforced directly in the bytecode.
Moreover, the constraints added by
inRangeSignedwere equivalent toTrueanyway.Checklist