rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2022-05-13	Revert "Auto merge of #12149 - jonas-schievink:literally-just-a-literal, ↵	Jonas Schievink	-17/+2
	r=jonas-schievink" This reverts commit cc9ae2b89e01a30e441371b9fd3376c3d03a475f, reversing changes made to 7dfd1cb572d8d4fd951237361e43ecddd9c9a852.
2022-05-05	Indicate the number of float tokens in the first token	Jonas Schievink	-1/+14

2022-05-05	Split float literal tokens at the `.`	Jonas Schievink	-3/+3

2022-05-05	Wrap float literals in their own node	Jonas Schievink	-0/+2

2022-05-05	Lower values of char and byte literals	Laurențiu Nicola	-1/+1

2022-04-05	Wrap macros in expr position in `MacroExpr` node	Jonas Schievink	-0/+1

2022-04-01	internal: Move rust.ungram into rust-analyzer/crates/syntax	Lukas Wirth	-2/+3

2022-03-05	fix: Recognize `Self` as a proper keyword	Lukas Wirth	-12/+16

2022-03-05	Merge #11598	bors[bot]	-0/+1
	11598: feat: Parse destructuring assignment r=Veykril a=ChayimFriedman2 Part of #11532. Lowering is not as easy and may not even be feasible right now as it requires generating identifiers: `(a, b) = (b, a)` is desugared into ```rust { let (<gensym_a>, <gensym_b>) = (b, a); a = <gensym_a>; b = <gensym_b>; } ``` rustc uses hygiene to implement that, but we don't support hygiene yet. However, I think parsing was the main problem as lowering will just affect type inference, and while `{unknown}` is not nice it's much better than a syntax error. I'm still looking for the best way to do lowering, though. Fixes #11454. Co-authored-by: Chayim Refael Friedman <chayimfr@gmail.com>
2022-03-02	Parse destructuring assignment	Chayim Refael Friedman	-0/+1
	The only patterns we should parse are `..` in structs and `_`: the rest are either not supported or already valid expressions.
2022-02-26	Fix body selection in while loops	Laurențiu Nicola	-2/+3

2022-02-21	Parse `let` expressions in order to support `let` chains	Chayim Refael Friedman	-1/+1
	We still need to reject freestanding `let` expressions: see https://github.com/rust-analyzer/rust-analyzer/issues/11320#issuecomment-1018212465.
2022-01-08	Allow doc comments on all `Item`s	Jonas Schievink	-1/+3

2022-01-07	Generate `AnyHasDocComments` node	Lukas Wirth	-0/+27

2021-12-26	internal: move inline parser tests to parser crate	Aleksey Kladov	-124/+0

2021-12-12	parser tests work	Aleksey Kladov	-0/+12

2021-10-30	Fix for-loop expressions breaking with BlockExpr iterable	Lukas Wirth	-4/+11

2021-10-28	Refactor ide handling for paths in derive inputs	Lukas Wirth	-1/+1

2021-10-23	internal: remove unused dollars	Aleksey Kladov	-10/+1

2021-10-19	internal: Parse const trait bounds	Lukas Wirth	-0/+1

2021-10-07	Support `let...else`	Jonas Schievink	-0/+1

2021-10-03	Fix miscellaneous Clippy lints	Aramis Razzaghipour	-7/+8

2021-10-02	minor: generated code readability	Aleksey Kladov	-1/+2

2021-09-27	Rename `Owner` traits to `Has`	Lukas Wirth	-8/+8

2021-09-27	Rename `Dyn` nodes to `Any` nodes	Lukas Wirth	-4/+4

2021-09-26	internal: more reasonable grammar for blocks	Aleksey Kladov	-1/+1
	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-25	minore: improve consistency	Aleksey Kladov	-8/+8

2021-09-21	Simplify	Lukas Wirth	-5/+1

2021-09-21	Simplify	Lukas Wirth	-7/+5

2021-09-21	Generate ast nodes for each ast trait	Lukas Wirth	-0/+61

2021-09-06	minor: modernize	Aleksey Kladov	-0/+1

2021-07-03	internal: overhaul code generation	Aleksey Kladov	-0/+1129
	* Keep codegen adjacent to the relevant crates. * Remove codgen deps from xtask, speeding-up from-source installation. This regresses the release process a bit, as it now needs to run the tests (and, by extension, compile the code).