AST, SIL: Remove UTF16 encoding from StringLiteralExpr and StringLiteralInst #33288
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
|
@swift-ci smoke test |
|
@swift-ci smoke test linux |
|
@swift-ci smoke test macOS |
DougGregor
approved these changes
Aug 6, 2020
…ralInst The UTF16 encoding is not used (anymore). I think it became obsolete with the switch to the UTF8 String representation.
eeckstein
force-pushed
the
string-optimization
branch
from
0d8e75d to
755f6aa
Compare
|
@swift-ci smoke test and merge |
1 similar comment
|
@swift-ci smoke test and merge |
|
@swift-ci smoke test macOS |
1 similar comment
|
@swift-ci smoke test macOS |
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.
The UTF16 encoding is not used (anymore). I think it became obsolete with the switch to the UTF8 String representation.