Skip to content

Conversation

@kroening
Copy link
Collaborator

The ACSL unicode operators are UTF-8, not UTF-16; also add missing ACSL
operators.

  • 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.
  • 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.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

The ACSL unicode operators are UTF-8, not UTF-16; also add missing ACSL
operators.
@tautschnig tautschnig merged commit 5e84ac2 into develop Oct 18, 2018
@tautschnig tautschnig deleted the acsl-operators branch October 18, 2018 08:30
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passed Diffblue compatibility checks (cbmc commit: 00c8512).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/88365396

@martin-cs
Copy link
Collaborator

Is ACSL now fully supported / documented / encouraged / working / a work-in-progress / of future interest / mainly of historical interest / deprecated?

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.

5 participants