4 commits

Author	SHA1	Message	Date
Aleksey Kladov	2bf81922f7	internal: more reasonable grammar for blocks ... Consider these expples { 92 } async { 92 } 'a: { 92 } #[a] { 92 } Previously the tree for them were BLOCK_EXPR { ... } EFFECT_EXPR async BLOCK_EXPR { ... } EFFECT_EXPR 'a: BLOCK_EXPR { ... } BLOCK_EXPR #[a] { ... } As you see, it gets progressively worse :) The last two items are especially odd. The last one even violates the balanced curleys invariant we have (#10357) The new approach is to say that the stuff in `{}` is stmt_list, and the block is stmt_list + optional modifiers BLOCK_EXPR STMT_LIST { ... } BLOCK_EXPR async STMT_LIST { ... } BLOCK_EXPR 'a: STMT_LIST { ... } BLOCK_EXPR #[a] STMT_LIST { ... }	2021-09-26 19:16:09 +03:00
Marijn Suijten	42da26e959	parser,syntax: Add separate parser for stmt with optional semicolon ... Adjusting `grammar::fragments::stmt` to Optional or Yes will break original functionality and tests.	2021-01-03 12:05:52 +01:00
Marijn Suijten	cc081b7e1c	syntax,ssr: Implement statement parsing	2021-01-03 11:29:33 +01:00
Aleksey Kladov	a1c187eef3	Rename ra_syntax -> syntax	2020-08-12 18:30:53 +02:00