-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Non ascii byte string literals broken #18697
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
Comments
Some people seem to think that ASCII isn't an encoding and that byte literal actually means ASCII literal. Restricting byte literals to ASCII makes unnecessary assumptions about the use of byte literals and actively discriminates against people using languages other than English. |
And, of course, the bytes! macro doesn't have this bug. |
rust-lang/rfcs#69 (see the It looks like this and the other shortcomings of byte string literals have been known for at least 4 months and yet neither have byte string literals been fixed nor has the bytes! macro been undeprecated. |
An issue such as this belongs on the RFC repo instead of this repository (it is a language change). |
internal: Simplify ratoml testdir usage
If this is by design then the design is wrong.
The text was updated successfully, but these errors were encountered: