[OrderedSet] Don't let the unchecked init create large sets with no hash table #107
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 debug builds, the
OrderedSet.init(uncheckedUniqueElements:)initializer always created a set with no hash table, even if it had an element count >15. This is technically an invariant violation (caught by_checkInvariants()), although it generally only triggers (very) slow performance. (The set reverts to linear searching.)Checklist