-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
benchmark: fix some RegExp nits #13551
Closed
Closed
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
nodejs-github-bot
added
benchmark
Issues and PRs related to the benchmark subsystem.
buffer
Issues and PRs related to the buffer subsystem.
crypto
Issues and PRs related to the crypto subsystem.
labels
Jun 8, 2017
vsemozhetbyt
removed
buffer
Issues and PRs related to the buffer subsystem.
crypto
Issues and PRs related to the crypto subsystem.
labels
Jun 8, 2017
cjihrig
approved these changes
Jun 8, 2017
tniessen
reviewed
Jun 8, 2017
// Parse configuration arguments | ||
for (const arg of argv) { | ||
const match = arg.match(/^(.+?)=([\s\S]*)$/); | ||
const match = arg.match(validArgRE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not validArgRE.test(arg)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is some match[capture_index] processing below.
refack
approved these changes
Jun 8, 2017
tniessen
approved these changes
Jun 8, 2017
lpinca
approved these changes
Jun 10, 2017
Landed in 8beff64 |
vsemozhetbyt
added a commit
that referenced
this pull request
Jun 12, 2017
* Take RegExp creation out of cycle. * use test(), not match() in boolean context. PR-URL: #13551 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
addaleax
pushed a commit
that referenced
this pull request
Jun 12, 2017
* Take RegExp creation out of cycle. * use test(), not match() in boolean context. PR-URL: #13551 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Merged
3 tasks
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.
Checklist
Affected core subsystem(s)
benchmark
RegExp
instance creation out of a cycle.test()
, notmatch()
in a boolean context.