rust/crates/syntax/test_data/parser/ok/0005_fn_item.rast

SOURCE_FILE@0..13
  FN@0..12
    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..12
      STMT_LIST@9..12
        L_CURLY@9..10 "{"
        WHITESPACE@10..11 "\n"
        R_CURLY@11..12 "}"
  WHITESPACE@12..13 "\n"
Convert tests to text-size 2020-04-24 16:51:02 -05:00			`SOURCE_FILE@0..13`
Rename FnDef -> Fn 2020-07-30 07:51:08 -05:00			`FN@0..12`
Convert tests to text-size 2020-04-24 16:51:02 -05:00			`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..12`
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@9..12`
			`L_CURLY@9..10 "{"`
			`WHITESPACE@10..11 "\n"`
			`R_CURLY@11..12 "}"`
Convert tests to text-size 2020-04-24 16:51:02 -05:00			`WHITESPACE@12..13 "\n"`