Sort: Change lexsort comment from stable to unstable#8245
Merged
mbrobbel merged 3 commits intoapache:mainfrom Aug 29, 2025
Merged
Sort: Change lexsort comment from stable to unstable#8245mbrobbel merged 3 commits intoapache:mainfrom
mbrobbel merged 3 commits intoapache:mainfrom
Conversation
mbrobbel
approved these changes
Aug 29, 2025
Member
mbrobbel
left a comment
mbrobbel
left a comment
There was a problem hiding this comment.
You can rebase/merge main to fix CI.
Co-authored-by: Matthijs Brobbel <m1brobbel@gmail.com>
mbrobbel
approved these changes
Aug 29, 2025
Member
|
Thanks @mapleFU |
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
2 participants
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.
Which issue does this PR close?
The doc for lexsort says it's stable. However, it's an unstable sort.
Rationale for this change
Fix the document.
What changes are included in this PR?
Fix the document.
Are these changes tested?
No need
Are there any user-facing changes?
Doc change