-
Notifications
You must be signed in to change notification settings - Fork 263
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
[Do not review just yet] Cleanup exprt and expr_util #8451
Draft
tautschnig
wants to merge
11
commits into
diffblue:develop
Choose a base branch
from
tautschnig:cleanup-expr
base: develop
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.
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
Cleaning of &&/|| introduced `GOTO` and `SKIP` instructions without a source location.
Removes one of the functions from the expr_util translation unit that is supposed to be deprecated.
Avoids use of the now-deprecated exprt methods.
The value representation is an implementation detail. Callers should use methods at a higher level of abstraction.
This will eventually replace `make_boolean_expr` to remove one of the functions from the expr_util translation unit, which is supposed to be deprecated.
When the operand can be a Boolean constant we can don't need to wait for simplify_exprt to clean up the avoidable not_exprt.
`make_and` does not necessarily produce an `and_exprt`, so its name is misleading. We already have `conjunction(exprt::operandst)`, and will now have a variant thereof that takes exactly two operands.
We did not consistently use it, and the three methods that did so can easily be adjusted to match the remaining ones in directly taking `exprt` instead.
This will eventually remove one of the functions from the expr_util translation unit, which is supposed to be deprecated.
This is no longer used and can easily be avoided by constructing a fixedbvt from an integer.
Use constructor chaining to avoid code duplication and remove the unused operator==(int).
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 PR combines a series of changes that will mostly become PRs of their own.