8 commits

Author	SHA1	Message	Date
Albert Larsan	cf2dff2b1e	Move /src/test to /tests	2023-01-11 09:32:08 +00:00
Nicholas Nethercote	7dbf2c0ed8	Make non-ASCII errors more consistent. ... 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.	2022-11-04 14:23:40 +11:00
Esteban Küber	3b5d018ebb	Handle Spans for byte and raw strings and add more detail	2021-02-03 13:34:28 -08:00
Vadim Petrochenkov	41a93cba38	Remove -Z continue-parse-after-error	2020-01-08 21:48:04 +03:00
varkor	5392f44a92	Remove unnecessary tidy ignore directives	2019-04-23 11:42:15 +01:00
Vadim Petrochenkov	1f64f60d5c	tests: Do not use -Z parse-only, continue compilation to test recovery	2019-01-06 22:20:46 +03:00
Mark Rousskov	2a663555dd	Remove licenses	2018-12-25 21:08:33 -07:00
Vadim Petrochenkov	73e1f8970f	Move parse-fail tests to UI	2018-10-21 14:06:28 +03:00

Renamed from src/test/parse-fail/byte-string-literals.rs (Browse further)