docs: clarify regex-lite word boundaries#1363
Merged
BurntSushi merged 1 commit intoJun 6, 2026
Merged
Conversation
BurntSushi
force-pushed
the
docs-regex-lite-word-boundary
branch
from
c95fdbf to
7e8aced
Compare
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.
Fixes #1356.
This clarifies in the
regex-litedifferences section that word boundary assertions such as\band\Bare ASCII-only because they are defined in terms of\wand\W.Validation:
git show --check --oneline HEADNot run locally:
cargo test -p regex-liteReason: this Windows environment does not currently have
cargoon PATH. The change is documentation-only and limited toregex-lite/src/lib.rs.AI-assisted contribution: implemented with OpenAI Codex and reviewed locally before submission.