Skip to content

Conversation

@hannes-steffenhagen-diffblue
Copy link
Contributor

This is fortunately only in a unit tests and apparently hasn’t caused any
problems so far, but we nevertheless should avoid returning references to
temporaries.

As a bonus the fixed code is simpler.

  • 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.
  • 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).
  • 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.

This is fortunately only in a unit tests and apparently hasn’t caused any
problems so far, but we nevertheless should avoid returning references to
temporaries.

As a bonus the fixed code is simpler.
Copy link
Collaborator

@martin-cs martin-cs left a comment

Choose a reason for hiding this comment

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

Yep; that definitely needs fixing.

@hannes-steffenhagen-diffblue hannes-steffenhagen-diffblue merged commit c12016b into diffblue:develop Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants