Skip to content

Conversation

@stephentoub
Copy link
Member

In rolling out usage of StringBuilder.Append's support for interpolated strings, I mistook this occurrence as a StringBuilder rather than a ValueStringBuidler. This reverts the changes to its ToString, but also switches to use EncodeToUtf16 rather than a custom loop.

In rolling out usage of StringBuilder.Append's support for interpolated strings, I mistook this occurrence as a StringBuilder rather than a ValueStringBuidler.  This reverts the changes to its ToString, but also switches to use EncodeToUtf16 rather than a custom loop.
@ghost
Copy link

ghost commented Jul 18, 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.

@ghost
Copy link

ghost commented Jul 18, 2021

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

Issue Details

In rolling out usage of StringBuilder.Append's support for interpolated strings, I mistook this occurrence as a StringBuilder rather than a ValueStringBuidler. This reverts the changes to its ToString, but also switches to use EncodeToUtf16 rather than a custom loop.

Author: stephentoub
Assignees: -
Labels:

area-System.Runtime

Milestone: -

@stephentoub stephentoub merged commit 1d0ee12 into dotnet:main Jul 18, 2021
@stephentoub stephentoub deleted the fixappidstring branch July 18, 2021 11:01
@ghost ghost locked as resolved and limited conversation to collaborators Aug 17, 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