Skip to content

Conversation

@jkoritzinsky
Copy link
Member

This enables SString to get out of the UTF16 state and helps move us away from "SString's natural encoding is UTF16".

This is the first of multiple PRs based on work in #69748.

This enables SString to get out of the UTF16 state and helps move us away from "SString's natural encoding is UTF16"
@jkoritzinsky jkoritzinsky requested a review from jkotas June 21, 2022 22:19
@ghost ghost added the area-VM-coreclr label Jun 21, 2022
@ghost ghost assigned jkoritzinsky Jun 21, 2022
Copy link
Member

@jkotas jkotas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Copy link
Member Author

@jkoritzinsky jkoritzinsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkotas same process applies for SetLiteral, correct?

@jkotas
Copy link
Member

jkotas commented Jun 21, 2022

@jkotas same process applies for SetLiteral, correct?

Yep

…w convert the SString itself and in some cases it was already in UTF8) and implement PR feedback.
@jkoritzinsky
Copy link
Member Author

@jkotas any more feedback?

Copy link
Member

@jkotas jkotas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you!

@jkotas jkotas merged commit d17741d into dotnet:main Jun 23, 2022
@jkoritzinsky jkoritzinsky deleted the sstring-getutf8 branch June 23, 2022 01:06
@ghost ghost locked as resolved and limited conversation to collaborators Jul 23, 2022
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.

3 participants