about summary refs log tree commit diff
path: root/src/test/ui/parser/byte-string-literals.rs
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-9/+0
2022-11-04Make non-ASCII errors more consistent.Nicholas Nethercote-2/+2
There are three kinds of "byte" literals: byte literals, byte string literals, and raw byte string literals. None are allowed to have non-ASCII chars in them. Two `EscapeError` variants exist for when that constraint is violated. - `NonAsciiCharInByte`: used for byte literals and byte string literals. - `NonAsciiCharInByteString`: used for raw byte string literals. As a result, the messages for raw byte string literals use different wording, without good reason. Also, byte string literals are incorrectly described as "byte constants" in some error messages. This commit eliminates `NonAsciiCharInByteString` so the three cases are handled similarly, and described correctly. The `mode` is enough to distinguish them. Note: Some existing error messages mention "byte constants" and some mention "byte literals". I went with the latter here, because it's a more correct name, as used by the Reference.
2021-02-03Handle `Span`s for byte and raw strings and add more detailEsteban Küber-2/+3
2020-01-08Remove `-Z continue-parse-after-error`Vadim Petrochenkov-2/+0
2019-04-23Remove unnecessary tidy ignore directivesvarkor-3/+0
2019-01-06tests: Do not use `-Z parse-only`, continue compilation to test recoveryVadim Petrochenkov-1/+1
2018-12-25Remove licensesMark Rousskov-10/+0
2018-10-21Move parse-fail tests to UIVadim Petrochenkov-0/+23