Skip to content

Conversation

GregTalotta
Copy link

I ran static analysis tools on the C++ code. Then fixed all warnings.

@ryanhaining
Copy link
Owner

The comparisons are done intentionally, the minimum requirements for an iterator that works with ranged-for include operator!= but not operator== so I only rely on the former. The iteratoriterator tests are verifying that the given operators work predictably.

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.

2 participants