aboutsummaryrefslogtreecommitdiff
path: root/xtask/src/codegen
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Specify literal tokensAleksey Kladov2020-07-312-1/+8
| | |
| * | MinorAleksey Kladov2020-07-311-7/+6
| |/
| * Rename LambdaExpr -> ClosureExprAleksey Kladov2020-07-312-9/+21
| |
| * Work on expressions grammarAleksey Kladov2020-07-312-157/+176
| |
| * Item is a StmtAleksey Kladov2020-07-312-1/+4
| |
| * Handwrite StmtAleksey Kladov2020-07-311-25/+26
| |
| * Move Stmt GrammarAleksey Kladov2020-07-311-11/+11
| |
| * Finalize WhereClause gramamrAleksey Kladov2020-07-311-7/+7
| |
| * Finalize TypeBound grammarAleksey Kladov2020-07-311-6/+7
| |
| * "Finalize" Types grammarAleksey Kladov2020-07-311-1/+1
| | | | | | | | | | | | | | 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-8/+8
| |
| * Rename TypeRef -> TypeAleksey Kladov2020-07-312-28/+34
| | | | | | | | | | | | | | | | | | | | 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.
| * ReorderAleksey Kladov2020-07-311-20/+20
| |
| * Use ty to access most TypeRefsAleksey Kladov2020-07-301-10/+10
| |
| * Remove TypeAscriptionOwnerAleksey Kladov2020-07-302-9/+8
| |
| * simplifyAleksey Kladov2020-07-301-3/+2
| |
| * Finalize attribute grammarAleksey Kladov2020-07-301-4/+1
| |
| * Dead codeAleksey Kladov2020-07-301-3/+0
| |
| * MinorAleksey Kladov2020-07-301-7/+6
| |
| * Finalize visibility grammarAleksey Kladov2020-07-301-3/+8
| |
| * Introduce GenericParamAleksey Kladov2020-07-301-18/+19
| |
| * Finaize item grammarAleksey Kladov2020-07-301-16/+16
| |
| * Finalize impl GrammarAleksey Kladov2020-07-301-4/+7
| |
| * Finalize Trait grammarAleksey Kladov2020-07-301-2/+2
| |
| * Fix param gramamrAleksey Kladov2020-07-301-2/+5
| |
| * Finalize const&static grammarAleksey Kladov2020-07-301-12/+12
| |
| * Finalize Enum grammarAleksey Kladov2020-07-301-1/+1
| |
| * Rename EnumVariant -> VariantAleksey Kladov2020-07-301-4/+4
| |
| * Rename EnumDef -> EnumAleksey Kladov2020-07-301-7/+7
| |
| * Rename StructDef -> StructAleksey Kladov2020-07-302-4/+4
| |
| * Finalize union grammarAleksey Kladov2020-07-301-3/+3
| |
| * Finalize structs grammarAleksey Kladov2020-07-301-4/+3
| |
| * SimplifyAleksey Kladov2020-07-301-34/+24
| |
| * Simplify codegenAleksey Kladov2020-07-301-21/+21
| |
| * Rename FieldDef -> FieldAleksey Kladov2020-07-301-13/+13
| |
| * Rename RecordLit -> RecordExprAleksey Kladov2020-07-301-6/+6
| |
| * Minor, reorderAleksey Kladov2020-07-301-4/+5
| |
| * Rename TypeParamList -> GenericParamListAleksey Kladov2020-07-302-11/+11
| |
| * Rename TypeAliasDef -> TypeAliasAleksey Kladov2020-07-301-6/+6
| |
| * Rename FnDef -> FnAleksey Kladov2020-07-302-24/+29
| |
| * Rename UseItem -> UseAleksey Kladov2020-07-301-2/+2
| |
| * Add comma list to use treeAleksey Kladov2020-07-302-12/+48
| |
| * Finish extern crates grammarAleksey Kladov2020-07-301-4/+4
| |
| * Rename RenameAleksey Kladov2020-07-301-3/+3
| |
| * Finish Module grammarAleksey Kladov2020-07-301-1/+1
| |
| * Split ItemList & AssocItemListAleksey Kladov2020-07-301-11/+12
| |
| * Finish SourceFile grammarAleksey Kladov2020-07-292-1/+2
| |
| * Rename ModuleItem -> ItemAleksey Kladov2020-07-291-20/+20
| |
| * Rename NomialDef -> AdtDefAleksey Kladov2020-07-291-1/+1
| |
| * Switch to ungrammar from ast_srcAleksey Kladov2020-07-292-4/+749
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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