-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: modernise GeometryHierarchyMap #3594
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm generally hesitant to replace iterators by vectors because iterators are more general, but in this it seems like this doesn't change the public API, and the type was fixed to vector anyway. So I am okay with this.
Invalidated by push of 55b5ddb
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't going back to hard coding vectors a step back? I don't understand why we're removing iterators here.
Nevermind, saw the other comments now.
iterator_t