bpo-34636: Use fast path for more chars in SRE category macros.#9170
Merged
Conversation
Member
|
Confirming the microoptimization here with a non-debug (opt) build: Those results are consistent across reruns. |
gpshead
approved these changes
Sep 11, 2018
gpshead
left a comment
Member
There was a problem hiding this comment.
I confirmed that the valued used make sense and match pyctype where the values are defined.
Contributor
|
@sir-sigurd: Status check is done, and it's a success ✅ . |
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
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.
When handling \s, \d, or \w (and their inverse) escapes in bytes regexes this a small but measurable performance improvement.
https://bugs.python.org/issue34636