[release/6.0] [mono] Use string.Empty for empty string custom arg values #58113
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.
Backport of #58023 to release/6.0
/cc @lambdageek @uweigand
Customer Impact
Discovered while running ASP.NET Core tests on the S390x port. Kestrel assumes that custom attribute values are reference-equal to
string.Empty
, not some other empty string value.Testing
Manual testing and CI
Risk
Very low - code would have to rely on Mono's custom attribute implementation to return fresh string objects to be affected.