Fix a bug where Forkable::LowerBound would sometimes return an incorrect iterator #1395
+79
−21
Conversation
This file contains hidden or 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
eggrobin
approved these changes
May 25, 2017
physics/forkable_body.hpp
Outdated
| } | ||
| if (!((*ancestry_it)->timeline_empty() || | ||
| (*fork_points_it && | ||
| **fork_points_it == (*ancestry_it)->timeline_end()))) { |
There was a problem hiding this comment.
Use De Morgan to make the comment reflect the condition.
|
Retest this please |
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.
In particular, if that iterator was at end we would be reading random memory. This manifested itself by markers (notably for apoasides) drawn in the middle of nowhere and by the inability to replay some journals.