Improve wg-quick regex performance when key or value is too large string#14
Open
firebroo wants to merge 1 commit intoWireGuard:masterfrom
Open
Improve wg-quick regex performance when key or value is too large string#14firebroo wants to merge 1 commit intoWireGuard:masterfrom
firebroo wants to merge 1 commit intoWireGuard:masterfrom
Conversation
4574b8e to
0b7d982
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
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 parse config file key or value is too large string, e.g,
My real scenario is that there is a large routing table allowedips,that will take long time when use regex with greed mode.