Repository navigation
sorts: type double_sort for any comparable items - #15345
Merged
cclauss merged 1 commit intoSep 18, 2026
Merged
Conversation
9 tasks done
Member
|
ON HOLD: Our focus is on merging or closing old pull requests before October 1st. |
cclauss
approved these changes
Sep 18, 2026
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
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.
Describe your change
Makes
double_sortgeneric over anyComparableitems instead oflist[Any], following the already-mergedinsertion_sort.pypattern (aComparableProtocolplus a[T: Comparable]type parameter). Comparisons already go through<only, so items only need__lt__.Part of #15234 (using "Part of", not a closing keyword, so the umbrella issue stays open).
Checklist
pytest.raises(TypeError)for non-comparable input.