Skip to content

Conversation

@stephentoub
Copy link
Member

For now, this helps reduce allocation if a rune or char is used as an argument to string.Format (including interpolated strings). Once ISpanFormattable (or whatever we decide to do as part of API review) is public as part of the improved support for interpolated strings, it'll help there further as well.

@ghost
Copy link

ghost commented Mar 26, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@stephentoub stephentoub added this to the 6.0.0 milestone Mar 26, 2021
For now, this helps reduce allocation if a rune or char is used as an argument to string.Format.  Once ISpanFormattable (or whatever we decide to do as part of API review) is public as part of the improved support for interpolated strings, it'll help there as well.
@stephentoub
Copy link
Member Author

Failure is #30056

@stephentoub stephentoub merged commit 2bdee5b into dotnet:main Mar 26, 2021
@stephentoub stephentoub deleted the runecharformat branch March 26, 2021 16:29
@ghost ghost locked as resolved and limited conversation to collaborators Apr 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants