Stop allocating unnecessary StringBuilders in ParsePropertyComments#6508
Merged
dipeshmsft merged 1 commit intodotnet:mainfrom Jun 3, 2022
Merged
Stop allocating unnecessary StringBuilders in ParsePropertyComments#6508dipeshmsft merged 1 commit intodotnet:mainfrom
dipeshmsft merged 1 commit intodotnet:mainfrom
Conversation
dipeshmsft
approved these changes
May 19, 2022
This was referenced Jun 9, 2022
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description
When we already have a StringBuilder, just clear it rather than allocating a replacement. Also don't ToString() only to then create a new string without the first character; use StringBuilder's ToString that takes an offset and length.
Customer Impact
Unnecessary allocation.
Regression
No
Testing
CI
Risk
Minimal
Microsoft Reviewers: Open in CodeFlow