This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Use const internally in corelib for Environment.NewLine #27013
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.
Anywhere Environment.NewLine was being used internal to corelib, instead changes it to use an internal Environment.NewLineConst, which is just a const string. The main benefit of that is places where it's then concatenated with another const allows the C# compiler to do the concat at compile time rather than at run time.
Where I was already touching the code, fixed a few places where additional strings were being created unnecessarily, e.g.
s += a; s += b;
will do twostring.Concat
calls each with two arguments, whereass += a + b;
will do just onestring.Concat
call with three arguments.