Skip to content

Conversation

tautschnig
Copy link
Collaborator

The value representation is an implementation detail. Callers should use methods at a higher level of abstraction.

  • Each commit message has a non-empty body, explaining why the change was made.
  • 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 value representation is an implementation detail. Callers should use
methods at a higher level of abstraction.
@tautschnig tautschnig changed the title Mark constant_exprt::value_is_zero_string protected Mark constant_exprt::value_is_zero_string protected [depends-on: 8675] Jul 28, 2025
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.

3 participants