Skip to content

SMT2 solver: remove spurious parenthesis in result output #7253

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

Merged
merged 1 commit into from
Oct 19, 2022

Conversation

tautschnig
Copy link
Collaborator

The output had more closing parentheses than opening ones.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

The output had more closing parentheses than opening ones.
@kroening
Copy link
Member

Should there be closing parentheses after the operands?

@tautschnig
Copy link
Collaborator Author

Should there be closing parentheses after the operands?

There is the closing parenthesis on line 156, if that’s the operands you are referring to?

@kroening kroening merged commit bf18c17 into diffblue:develop Oct 19, 2022
@tautschnig tautschnig deleted the bugfixes/smt2-par branch October 20, 2022 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants