Aleksey Kladov da8eb29a2f Macro patterns are not confused with expressions. ... We treat macro calls as expressions (there's appropriate Into impl), which causes problem if there's expresison and non-expression macro in the same node (like in the match arm). We fix this problem by nesting macor patterns into another node (the same way we nest path into PathExpr or PathPat). Ideally, we probably should add a similar nesting for macro expressions, but that needs some careful thinking about macros in blocks: `{ am_i_expression!() }`.		2020-04-03 16:12:38 +02:00
..
lexer	ra_syntax: added tests for tokenization errors	2020-02-04 00:00:55 +02:00
parser	Macro patterns are not confused with expressions.	2020-04-03 16:12:38 +02:00
reparse/fuzz-failures	move syntax tests to unit tests	2019-07-24 12:49:19 +03:00
accidentally_quadratic	Add a test	2020-01-15 16:52:28 +01:00