Clarify that x{n}? behaves the same as x{n}
#42271
Open
+4
−0
Conversation
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
Added a note explaining that `x{n}?` behaves the same as `x{n}` because `{n}` is fixed-length and the lazy modifier has no effect.
github-actions
bot
added
Content:JS
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
files/en-us/web/javascript/guide/regular_expressions/cheatsheet/index.md
Outdated
Show resolved
Hide resolved
…t/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
| <li><code>/<.*?>/</code> will match "<foo>"</li> | ||
| </ul> | ||
| <p> | ||
| <b>Note:</b> Adding <code>?</code> after <code>{n}</code> doesn't change the match. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
error MD033/no-inline-html Inline HTML [Element: b]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #42270
Added a note explaining that
x{n}?behaves the same asx{n}because{n}is fixed-length and the lazy modifier has no effect.Description
Clarifies the behavior of
x{n}?by adding a note explaining that it behaves the same asx{n}.Motivation
This avoids confusion by clearly stating that the
?lazy modifier has no effect on fixed-length quantifiers like{n}.Additional details
Documentation-only change. No code or behavior is modified.
Related issues and pull requests
Fixes #42270