Specialize CombinationsWithReplacement::nth
#923
Merged
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.
Similarly to #914, I reorder
CombinationsWithReplacement::next
then specializeCombinationsWithReplacement::nth
.Benchmarks similar to #916 (comment)
I did not expect
next
to be a bit faster but I'm not complaining..nth(0)
is a little bit slower but other.nth(..)
s are faster, closely following allocations changes.