add documentation for feature utf16
#95
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
|
Thank you! |
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.
I've been looking for a regex impl for my toy JavaScript implementation (mcjs), and I thought
regresssounded good but still insufficient due to the lack of support for searching on UTF-16 strings.Turns out,
regressdoes do exactly what I need! It's just nowhere to be found in the crate documentation (at least not without following the 'Feature flags' link, which I had no reason to, I think). I only found this out by looking at what boa does for its own RegExp implementation.So, I hope this little extra paragraph will be useful for the next one who walks my path.
Let me know if you'd like me to change the format or rephrase the text.