9 Commits

Author	SHA1	Message	Date
Jonathan Brouwer	e0bdc46d94	Update uitest stderr ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-08-28 20:05:04 +02:00
Jonathan Brouwer	2c7dfa91b5	Add another case to the bad-lit-suffixes test ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-08-28 19:23:55 +02:00
Jonathan Brouwer	7db1840569	Changes to the uitests ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-08-27 20:25:18 +02:00
Jonathan Brouwer	149bdde97e	Fix #[must_use = 1] not giving an error ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-07-01 16:10:05 +02:00
Jonathan Brouwer	f98ea3d144	Port #[rustc_layout_scalar_valid_range_start/end] to the new attribute parsing infrastructure ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-06-27 09:08:21 +02:00
Jonathan Brouwer	b24df42488	Port #[must_use] to new attribute parsing infrastructure ... Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>	2025-06-22 14:51:58 +02:00
Mara Bos	585c9765a2	Update tests.	2025-01-07 16:04:14 +01:00
Nicholas Nethercote	226edf64fa	Improve an error involving attribute values. ... Attribute values must be literals. The error you get when that doesn't hold is pretty bad, e.g.: ``` unexpected expression: 1 + 1 ``` You also get the same error if the attribute value is a literal, but an invalid literal, e.g.: ``` unexpected expression: "foo"suffix ``` This commit does two things. - Changes the error message to "attribute value must be a literal", which gives a better idea of what the problem is and how to fix it. It also no longer prints the invalid expression, because the carets below highlight it anyway. - Separates the "not a literal" case from the "invalid literal" case. Which means invalid literals now get the specific error at the literal level, rather than at the attribute level.	2023-12-12 15:54:25 +11:00
Albert Larsan	cf2dff2b1e	Move /src/test to /tests	2023-01-11 09:32:08 +00:00