mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
52f5af7165
rust/crates/syntax/test_data/parser/inline/ok/0075_block.rast

91 lines
2.2 KiB
Plaintext
Raw Normal View History

Convert tests to text-size
2020-04-24 16:51:02 -05:00
SOURCE_FILE@0..65
Rename FnDef -> Fn
2020-07-30 07:51:08 -05:00
FN@0..9
Convert tests to text-size
2020-04-24 16:51:02 -05:00
FN_KW@0..2 "fn"
WHITESPACE@2..3 " "
NAME@3..4
IDENT@3..4 "a"
PARAM_LIST@4..6
L_PAREN@4..5 "("
R_PAREN@5..6 ")"
WHITESPACE@6..7 " "
BLOCK_EXPR@7..9
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 04:12:57 -05:00
STMT_LIST@7..9
L_CURLY@7..8 "{"
R_CURLY@8..9 "}"
Convert tests to text-size
2020-04-24 16:51:02 -05:00
WHITESPACE@9..10 "\n"
Rename FnDef -> Fn
2020-07-30 07:51:08 -05:00
FN@10..31
Convert tests to text-size
2020-04-24 16:51:02 -05:00
FN_KW@10..12 "fn"
WHITESPACE@12..13 " "
NAME@13..14
IDENT@13..14 "b"
PARAM_LIST@14..16
L_PAREN@14..15 "("
R_PAREN@15..16 ")"
WHITESPACE@16..17 " "
BLOCK_EXPR@17..31
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 04:12:57 -05:00
STMT_LIST@17..31
L_CURLY@17..18 "{"
WHITESPACE@18..19 " "
LET_STMT@19..29
LET_KW@19..22 "let"
WHITESPACE@22..23 " "
WILDCARD_PAT@23..24
UNDERSCORE@23..24 "_"
WHITESPACE@24..25 " "
EQ@25..26 "="
WHITESPACE@26..27 " "
LITERAL@27..28
INT_NUMBER@27..28 "1"
SEMICOLON@28..29 ";"
WHITESPACE@29..30 " "
R_CURLY@30..31 "}"
Convert tests to text-size
2020-04-24 16:51:02 -05:00
WHITESPACE@31..32 "\n"
Rename FnDef -> Fn
2020-07-30 07:51:08 -05:00
FN@32..48
Convert tests to text-size
2020-04-24 16:51:02 -05:00
FN_KW@32..34 "fn"
WHITESPACE@34..35 " "
NAME@35..36
IDENT@35..36 "c"
PARAM_LIST@36..38
L_PAREN@36..37 "("
R_PAREN@37..38 ")"
WHITESPACE@38..39 " "
BLOCK_EXPR@39..48
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 04:12:57 -05:00
STMT_LIST@39..48
L_CURLY@39..40 "{"
WHITESPACE@40..41 " "
EXPR_STMT@41..43
LITERAL@41..42
INT_NUMBER@41..42 "1"
SEMICOLON@42..43 ";"
WHITESPACE@43..44 " "
EXPR_STMT@44..46
LITERAL@44..45
INT_NUMBER@44..45 "2"
SEMICOLON@45..46 ";"
WHITESPACE@46..47 " "
R_CURLY@47..48 "}"
Convert tests to text-size
2020-04-24 16:51:02 -05:00
WHITESPACE@48..49 "\n"
Rename FnDef -> Fn
2020-07-30 07:51:08 -05:00
FN@49..64
Convert tests to text-size
2020-04-24 16:51:02 -05:00
FN_KW@49..51 "fn"
WHITESPACE@51..52 " "
NAME@52..53
IDENT@52..53 "d"
PARAM_LIST@53..55
L_PAREN@53..54 "("
R_PAREN@54..55 ")"
WHITESPACE@55..56 " "
BLOCK_EXPR@56..64
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 04:12:57 -05:00
STMT_LIST@56..64
L_CURLY@56..57 "{"
WHITESPACE@57..58 " "
EXPR_STMT@58..60
LITERAL@58..59
INT_NUMBER@58..59 "1"
SEMICOLON@59..60 ";"
WHITESPACE@60..61 " "
LITERAL@61..62
INT_NUMBER@61..62 "2"
WHITESPACE@62..63 " "
R_CURLY@63..64 "}"
Convert tests to text-size
2020-04-24 16:51:02 -05:00
WHITESPACE@64..65 "\n"
Reference in New Issue Copy Permalink