Josh Triplett 0b855bcdc9 Switch to a bitflags MacroKinds to support macros with more than one kind
Review everything that uses `MacroKind`, and switch anything that could
refer to more than one kind to use `MacroKinds`.

Add a new `SyntaxExtensionKind::MacroRules` for `macro_rules!` macros,
using the concrete `MacroRulesMacroExpander` type, and have it track
which kinds it can handle. Eliminate the separate optional `attr_ext`,
now that a `SyntaxExtension` can handle multiple macro kinds.

This also avoids the need to downcast when calling methods on
`MacroRulesMacroExpander`, such as `get_unused_rule`.

Integrate macro kind checking into name resolution's
`sub_namespace_match`, so that we only find a macro if it's the right
type, and eliminate the special-case hack for attributes.
2025-08-12 09:24:45 -07:00
..
2025-07-01 19:00:21 +00:00
2025-06-30 20:42:27 +10:00
2025-04-03 09:22:21 +00:00
2025-07-20 09:50:58 +00:00
2025-07-31 14:19:27 +02:00
2025-07-31 14:19:27 +02:00
2025-07-31 14:19:27 +02:00
2025-06-24 04:05:27 +00:00
2025-07-31 14:19:27 +02:00