rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-09-21	Changes to uitests for macro_export port	Jonathan Brouwer	-3/+9
	Co-authored-by: Anne Stijns <anstijns@gmail.com>
2025-04-17	Replace infallible `name_or_empty` methods with fallible `name` methods.	Nicholas Nethercote	-2/+2
	I'm removing empty identifiers everywhere, because in practice they always mean "no identifier" rather than "empty identifier". (An empty identifier is impossible.) It's better to use `Option` to mean "no identifier" because you then can't forget about the "no identifier" possibility. Some specifics: - When testing an attribute for a single name, the commit uses the `has_name` method. - When testing an attribute for multiple names, the commit uses the new `has_any_name` method. - When using `match` on an attribute, the match arms now have `Some` on them. In the tests, we now avoid printing empty identifiers by not printing the identifier in the `error:` line at all, instead letting the carets point out the problem.
2025-04-17	Augment some tests involving attributes.	Nicholas Nethercote	-0/+6
	This shows places where the use of `name_or_empty` causes problems, i.e. we print empty identifiers in error messages: ``` error: unrecognized field name `` error: `` isn't a valid `#[macro_export]` argument `#[no_sanitize()]` should be applied to a function ``` (The last one is about an attribute `#[no_sanitize("address")]`.) The next commit will fix these.
2024-02-16	[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives	许杰友 Jieyou Xu (Joe)	-2/+2

2023-04-27	Add invalid_macro_export_arguments to built-in macro list	Michael Goulet	-3/+10

2023-02-22	Add check for invalid \`#[macro_export]\` arguments	blyxyas	-0/+26