macOS: Move util::EMPTY_RANGE to usage spot
#3685
Merged
Conversation
This file contains 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
madsmtm
force-pushed
the
madsmtm/macos-empty-range
branch
from
1a19cbb to
3125987
Compare
kchibisov
approved these changes
May 6, 2024
kchibisov
force-pushed
the
madsmtm/macos-empty-range
branch
from
3125987 to
8a6e483
Compare
notgull
pushed a commit
that referenced
this pull request
Jun 1, 2024
kchibisov
pushed a commit
that referenced
this pull request
Jun 10, 2024
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.
Just a small code cleanup, the range is not actually empty (that'd be
NSRange::new(0, 0)), rather, this behaviour is specific tomarkedRangeandselectedRange.