aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax
Commit message (Collapse)AuthorAgeFilesLines
...
* Rename RenameAleksey Kladov2020-07-303-10/+10
|
* Finish Module grammarAleksey Kladov2020-07-301-0/+1
|
* Update testsAleksey Kladov2020-07-3032-38/+38
|
* Split ItemList & AssocItemListAleksey Kladov2020-07-302-24/+56
|
* Finish SourceFile grammarAleksey Kladov2020-07-291-1/+3
|
* Rename ModuleItem -> ItemAleksey Kladov2020-07-294-388/+388
|
* Rename NomialDef -> AdtDefAleksey Kladov2020-07-291-19/+19
|
* Switch to ungrammar from ast_srcAleksey Kladov2020-07-293-2204/+824
| | | | | | | | | | | | | | | | | | The primary advantage of ungrammar is that it (eventually) allows one to describe concrete syntax tree structure -- with alternatives and specific sequence of tokens & nodes. That should be re-usable for: * generate `make` calls * Rust reference * Hypothetical parser's evented API We loose doc comments for the time being unfortunately. I don't think we should add support for doc comments to ungrammar -- they'll make grammar file hard to read. We might supply docs as out-of band info, or maybe just via a reference, but we'll think about that once things are no longer in flux
* Dead codeAleksey Kladov2020-07-291-41/+0
|
* Remove dead codeAleksey Kladov2020-07-291-3/+1
|
* Remove dead codeAleksey Kladov2020-07-291-46/+0
|
* Fix nameref parsingAleksey Kladov2020-07-281-2/+1
|
* Rename modulesAleksey Kladov2020-07-234-8/+9
|
* Store macro invocation parameters as text instead of ttLaurențiu Nicola2020-07-222-4/+4
|
* Bump lexerkjeremy2020-07-201-1/+1
|
* Move remove_bounds to edit.rsJonas Schievink2020-07-142-13/+15
|
* missing impl members: remove assoc. type boundsJonas Schievink2020-07-141-0/+13
|
* Comment decorationsAleksey Kladov2020-07-121-1/+4
| | | | closes #4461
* Make slow test parallelAleksey Kladov2020-07-112-18/+30
|
* Don't mess with cursor position when adding hashesAleksey Kladov2020-07-091-6/+11
|
* SimplifyAleksey Kladov2020-07-091-1/+2
|
* Unify testsAleksey Kladov2020-07-092-34/+3
|
* Clippy perf warningskjeremy2020-07-061-6/+2
| | | | Removes redundant clones
* Unify magic env var nameAleksey Kladov2020-07-011-1/+1
|
* Move parser specific tests utils to parser testsAleksey Kladov2020-07-011-1/+99
|
* Update the rest of the testsAleksey Kladov2020-06-291-0/+4
|
* Simlify with matches!()Veetaha2020-06-283-16/+10
|
* Bump rustc_lexerLaurențiu Nicola2020-06-272-13/+13
|
* Fix panic in split and merge import assistsLaurențiu Nicola2020-06-233-3/+18
|
* Merge #4962bors[bot]2020-06-2129-1/+222
|\ | | | | | | | | | | | | | | 4962: Implement APIs for parsing expressions, types, paths, patterns and items r=davidlattimore a=davidlattimore Co-authored-by: David Lattimore <[email protected]>
| * Implement APIs for parsing expressions, types, paths, patterns and itemsDavid Lattimore2020-06-2129-1/+222
| |
* | Merge #4851bors[bot]2020-06-191-0/+4
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 4851: Add quickfix to add a struct field r=TimoFreiberg a=TimoFreiberg Related to #4563 I created a quickfix for record literals first because the NoSuchField diagnostic was already there. To offer that quickfix for FieldExprs with unknown fields I'd need to add a new diagnostic (or create a `NoSuchField` diagnostic for those cases) I think it'd make sense to make this a snippet completion (to select the generated type), but this would require changing the `Analysis` API and I'd like some feedback before I touch that. Co-authored-by: Timo Freiberg <[email protected]>
| * Add quickfix to add a struct fieldTimo Freiberg2020-06-121-0/+4
| |
* | Merge #4872bors[bot]2020-06-181-46/+43
|\ \ | | | | | | | | | | | | | | | | | | | | | 4872: Reduce the usage of bare subscript operator r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
| * | Reduce the usage of bare subscript operatorVeetaha2020-06-141-46/+43
| |/
* | Merge #4878bors[bot]2020-06-161-0/+8
|\ \ | | | | | | | | | | | | | | | | | | | | | 4878: Make "Replace qualified name with use" replace *all* mentions of the path r=matklad a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/4836 Co-authored-by: Jonas Schievink <[email protected]>
| * | Fix `rewrite_root` when there's only 1 replacementJonas Schievink2020-06-131-0/+8
| |/
* | Make ra_syntax::{SyntaxNodeChildren, SyntaxElementChildren} public.David Lattimore2020-06-151-1/+2
| | | | | | | | SyntaxNode::children and SyntaxNode::children_with_tokens return these types, but there's currently no way AFAIK to name them.
* | Update parser tests with env varAleksey Kladov2020-06-151-1/+0
|/
* Merge #4855bors[bot]2020-06-122-141/+141
|\ | | | | | | | | | | | | | | 4855: Use more idiomatic style for lifetimes in generated code r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
| * Apply codegen with idiomatic lifetimesVeetaha2020-06-112-141/+141
| |
* | SimplifyVeetaha2020-06-121-5/+5
|/
* Add example of old trait object syntaxMatthew Jasper2020-06-112-1/+38
|
* Move complex inline test to own fileMatthew Jasper2020-06-116-356/+670
|
* Separating parsing of `for` in predicates and typesMatthew Jasper2020-06-109-282/+477
|
* Correctly parse <_> paths in patternsAleksey Kladov2020-06-093-37/+76
| | | | closes #3659
* Merge #4812bors[bot]2020-06-091-4/+9
|\ | | | | | | | | | | | | | | | | | | | | 4812: Use correct indent when replacing with match r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Use correct indent when replacing with matchAleksey Kladov2020-06-091-4/+9
| |
* | Parse default unsafe fnAvi Dessauer2020-06-082-0/+43
|/
* Fix bug in lexer for format specifier where the `type` and `width` were not ↵Leander Tentrup2020-06-071-14/+23
| | | | correctly distinguished