Fix performance issue for regexp in Reporting.kt #4550
Merged
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.
A regexp object is compiled into an internal data structure during initialization.
This could to a potential performance impact, if the
Regex()
constructor is called multiple times for the same pattern.Since the private function
truncatedMessage()
could be called a lot, this PR fixes this potential performance issue.Because of the overhead of object instantiation and regular expression compilation, reusing the initialized object is the recommended way.