Add two to four bytes utf8 character tests #2495
Merged
Conversation
This file contains 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
2 tasks
2 tasks
|
Regarding the 4-byte character problem, see #2522. |
dcodeIO
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the repo missed the tests for 2 bytes utf-8 character, 3 bytes utf-8 character and 4 bytes utf-8 character (4 bytes utf-8 character cannot bypass the parser phase, not sure if it is by design, for example charactor: 饾啈).
This PR attampts to add tests for global parameter name with utf-8 character, 3 bytes utf-8 character, AS will call allocString and alloc this utf-8 string to binary.
