Handle KLLVM.StringBuffer.contents
as bytes
and enable unicode
tests in String
contructors
#4567
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.
Blocked on #1126.
Related to:
StringPattern.contents
is broken llvm-backend#824UnicodeDecodeError
on non-utf bytes in terms of sortBytes
llvm-backend#1078This PR aims to support the new feature introduced in #1126 that makes
KLLVM.StringBuffer.contents
returnsbytes
. To ensure the symmetric behavior, we should also construct theKLLVM.StringBuffer
object with bytes. To ensure this feature works properly, we're usingraw_unicode_escape
encoding to pass and retrieve the result.This can be used as a first step in a new attempt to support Unicode!