dbb702cfc1
FragmentKind played two roles: * entry point to the parser * syntactic category of a macro call These are different use-cases, and warrant different types. For example, macro can't expand to visibility, but we have such fragment today. This PR introduces `ExpandsTo` enum to separate this two use-cases. I suspect we might further split `FragmentKind` into `$x:specifier` enum specific to MBE, and a general parser entry point, but that's for another PR! |
||
---|---|---|
.. | ||
ast_id_map.rs | ||
builtin_attr.rs | ||
builtin_derive.rs | ||
builtin_macro.rs | ||
db.rs | ||
eager.rs | ||
hygiene.rs | ||
lib.rs | ||
name.rs | ||
proc_macro.rs | ||
quote.rs | ||
test_db.rs |