rust/crates/syntax/test_data/parser/inline/ok/0151_fn.rast

SOURCE_FILE@0..12
  FN@0..11
    FN_KW@0..2 "fn"
    WHITESPACE@2..3 " "
    NAME@3..6
      IDENT@3..6 "foo"
    PARAM_LIST@6..8
      L_PAREN@6..7 "("
      R_PAREN@7..8 ")"
    WHITESPACE@8..9 " "
    BLOCK_EXPR@9..11
      STMT_LIST@9..11
        L_CURLY@9..10 "{"
        R_CURLY@10..11 "}"
  WHITESPACE@11..12 "\n"
Cleanup parser modifiers tests 2020-08-12 14:52:37 +02:00			`SOURCE_FILE@0..12`
			`FN@0..11`
			`FN_KW@0..2 "fn"`
			`WHITESPACE@2..3 " "`
			`NAME@3..6`
			`IDENT@3..6 "foo"`
			`PARAM_LIST@6..8`
			`L_PAREN@6..7 "("`
			`R_PAREN@7..8 ")"`
			`WHITESPACE@8..9 " "`
			`BLOCK_EXPR@9..11`
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 12:12:57 +03:00			`STMT_LIST@9..11`
			`L_CURLY@9..10 "{"`
			`R_CURLY@10..11 "}"`
Cleanup parser modifiers tests 2020-08-12 14:52:37 +02:00			`WHITESPACE@11..12 "\n"`