7 Commits

Author	SHA1	Message	Date
Maybe Waffle	94470f4efd	Use as_deref in compiler (but only where it makes sense)	2022-11-16 21:58:58 +00:00
Nicholas Nethercote	d6c97a32b4	Simplify unescape_{char,byte}. ... The `usize` isn't needed in the error case.	2022-11-08 15:59:19 +11:00
Nicholas Nethercote	a838952239	Remove unescape_byte_literal. ... It's easy to just use `unescape_literal` + `byte_from_char`.	2022-11-05 13:56:36 +11: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
Anton Golov	a03fbfe2ff	Warn when an escaped newline skips multiple lines	2021-08-11 11:35:08 +02:00
Anton Golov	5d59b4412e	Add warning when whitespace is not skipped after an escaped newline.	2021-07-30 16:26:39 +02:00
mark	9e5f7d5631	mv compiler to compiler/	2020-08-30 18:45:07 +03:00