aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/ast
Commit message (Collapse)AuthorAgeFilesLines
* Fix leading colonAleksey Kladov2020-07-311-1/+1
|
* Fix const arguments grammarAleksey Kladov2020-07-311-260/+259
|
* Fix GenericArgs grammarAleksey Kladov2020-07-311-19/+66
|
* Rename TypeArgList -> GenericArgListAleksey Kladov2020-07-312-11/+11
|
* Finalize Path grammarAleksey Kladov2020-07-311-446/+447
|
* MinorAleksey Kladov2020-07-311-68/+62
|
* Rename LambdaExpr -> ClosureExprAleksey Kladov2020-07-311-21/+14
|
* Work on expressions grammarAleksey Kladov2020-07-311-659/+669
|
* Item is a StmtAleksey Kladov2020-07-312-4/+10
|
* Handwrite StmtAleksey Kladov2020-07-312-25/+34
|
* Move Stmt GrammarAleksey Kladov2020-07-311-84/+85
|
* Finalize TypeBound grammarAleksey Kladov2020-07-312-47/+27
|
* "Finalize" Types grammarAleksey Kladov2020-07-311-1/+3
| | | | | | | Note that `for` type is rust-analyzer's own invention. Both the reference and syn allow `for` only for fnptr types, and we allow them everywhere. This needs to be checked with respect to type bounds grammar...
* Reame PlaceholderType -> InferTypeAleksey Kladov2020-07-311-11/+11
|
* Rename TypeRef -> TypeAleksey Kladov2020-07-313-135/+135
| | | | | | | | | | The TypeRef name comes from IntelliJ days, where you often have both type *syntax* as well as *semantical* representation of types in scope. And naming both Type is confusing. In rust-analyzer however, we use ast types as `ast::Type`, and have many more semantic counterparts to ast types, so avoiding name clash here is just confusing.
* Merge #5610bors[bot]2020-07-301-2/+1
|\ | | | | | | | | | | | | | | 5610: Bump deps r=flodiebold a=lnicola Co-authored-by: LaurenČ›iu Nicola <[email protected]>
| * Fix typoLaurențiu Nicola2020-07-301-2/+1
| |
| * Rename UseItem -> UseAleksey Kladov2020-07-303-17/+18
| |
| * Add comma list to use treeAleksey Kladov2020-07-301-77/+78
| |
* | Use ty to access most TypeRefsAleksey Kladov2020-07-301-10/+10
| |
* | Remove TypeAscriptionOwnerAleksey Kladov2020-07-302-13/+7
| |
* | simplifyAleksey Kladov2020-07-301-18/+18
| |
* | Finalize attribute grammarAleksey Kladov2020-07-302-56/+13
| |
* | Dead codeAleksey Kladov2020-07-301-102/+76
| |
* | Introduce GenericParamAleksey Kladov2020-07-302-85/+149
| |
* | Finaize item grammarAleksey Kladov2020-07-301-64/+71
| |
* | Finalize impl GrammarAleksey Kladov2020-07-302-17/+18
| |
* | Finalize Trait grammarAleksey Kladov2020-07-302-17/+17
| |
* | Finalize const&static grammarAleksey Kladov2020-07-302-44/+45
| |
* | Rename EnumVariant -> VariantAleksey Kladov2020-07-302-17/+17
| |
* | Rename EnumDef -> EnumAleksey Kladov2020-07-302-24/+24
| |
* | Rename StructDef -> StructAleksey Kladov2020-07-302-23/+23
| |
* | Finalize union grammarAleksey Kladov2020-07-302-22/+22
| |
* | Finalize structs grammarAleksey Kladov2020-07-301-1/+0
| |
* | Rename FieldDef -> FieldAleksey Kladov2020-07-303-57/+53
| |
* | Rename RecordLit -> RecordExprAleksey Kladov2020-07-305-38/+40
| |
* | Rename TypeParamList -> GenericParamListAleksey Kladov2020-07-303-18/+18
| |
* | Rename TypeAliasDef -> TypeAliasAleksey Kladov2020-07-303-50/+48
| |
* | Rename FnDef -> FnAleksey Kladov2020-07-305-211/+214
| |
* | Rename UseItem -> UseAleksey Kladov2020-07-303-17/+18
| |
* | Add comma list to use treeAleksey Kladov2020-07-301-77/+78
|/
* Finish extern crates grammarAleksey Kladov2020-07-301-62/+62
|
* Update testsAleksey Kladov2020-07-301-2/+6
|
* Rename RenameAleksey Kladov2020-07-303-10/+10
|
* Finish Module grammarAleksey Kladov2020-07-301-0/+1
|
* Split ItemList & AssocItemListAleksey Kladov2020-07-302-24/+56
|
* Finish SourceFile grammarAleksey Kladov2020-07-291-1/+3
|
* Rename ModuleItem -> ItemAleksey Kladov2020-07-292-385/+385
|
* 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