New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update string and xstring encodings #9142
Conversation
@@ -4212,9 +4212,9 @@ pm_encoding_shift_jis_char_width(const uint8_t *b, ptrdiff_t n) { | |||
} | |||
|
|||
/** | |||
* This is the definition of all of the encodings that we support. | |||
* This is the table of all of the encodings that prisms supports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* This is the table of all of the encodings that prisms supports. | |
* This is the table of all of the encodings that prism supports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes are on prism's side, so I'll update them there.
} pm_encoding_type_t; | ||
|
||
/** | ||
* This is the default UTF-8 encoding. We need it to quickly create parsers. | ||
* This is the table of all of the encodings that prisms supports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* This is the table of all of the encodings that prisms supports. | |
* This is the table of all of the encodings that prism supports. |
This merges ruby/prism#1990 and correctly sets encodings for string and xstring nodes. It does not set the correct encoding for individual pieces of interpolated string and interpolated xstring nodes, only because I want to get this merged first and then figure out what is missing.