Text indexing - docs update, and fixing AutomergeText updating for multi-byte Characters #99
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
heckj
force-pushed
the
text_index_docs_update
branch
from
f9e58df to
9b761e9
Compare
heckj
force-pushed
the
text_index_docs_update
branch
from
7ced87e to
676137e
Compare
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.
Fixing docs about index positions in Automerge - they're not UTF8 view positions, but UnicodeScalars - and the whole update process for AutomergeText fails badly with complex unicode characters (example: "🇬🇧👨👨👧👦😀")