#2117: location: add new assertions to detect duplicate insertions #2118
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
lifflander
force-pushed
the
2117-check-for-duplication-elements-during-collection-insertion
branch
from
b5db4aa to
99fb383
Compare
PhilMiller
reviewed
Mar 28, 2023
|
|
||
| // Invoke getCollectionLM() to create a new location manager instance for | ||
| // this collection | ||
| theLocMan()->getCollectionLM<IndexType>(proxy); |
Member
There was a problem hiding this comment.
Kinda ugly that a method named getFoo has a side effect of creating said Foo
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.
Fixes #2117