use valdi unicode conversions api instead of deprecated c++ apis #210
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
li-feng-sc
approved these changes
Nov 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This change updates the string conversions API for Valdi to use the the Valdi native unicode helpers instead of the deprecated C++ APIs. This change was checked in in master but got overriden a few days ago because the unicode change was not part of upstream. This PR fixes this by bringing the change upstream.
Changes:
StaticString::utf8ToWString()to convert a Valdi interned string to a C++ wstring. Under the hood, it detects at compile time the representation of wstring (utf16 or utf32) and uses the right conversion.StaticString::makeWithWideChars()to create a StaticString from a C++ wstring.