aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/ast/generated
Commit message (Collapse)AuthorAgeFilesLines
* Rename FieldDef -> FieldAleksey Kladov2020-07-301-50/+46
|
* Rename RecordLit -> RecordExprAleksey Kladov2020-07-301-24/+26
|
* Rename TypeParamList -> GenericParamListAleksey Kladov2020-07-301-15/+15
|
* Rename TypeAliasDef -> TypeAliasAleksey Kladov2020-07-301-47/+45
|
* Rename FnDef -> FnAleksey Kladov2020-07-301-206/+209
|
* Rename UseItem -> UseAleksey Kladov2020-07-301-14/+15
|
* Add comma list to use treeAleksey Kladov2020-07-301-77/+78
|
* Finish extern crates grammarAleksey Kladov2020-07-301-62/+62
|
* Rename RenameAleksey Kladov2020-07-301-8/+8
|
* Finish Module grammarAleksey Kladov2020-07-301-0/+1
|
* Split ItemList & AssocItemListAleksey Kladov2020-07-301-21/+50
|
* Finish SourceFile grammarAleksey Kladov2020-07-291-1/+3
|
* Rename ModuleItem -> ItemAleksey Kladov2020-07-291-384/+384
|
* Rename NomialDef -> AdtDefAleksey Kladov2020-07-291-19/+19
|
* Switch to ungrammar from ast_srcAleksey Kladov2020-07-291-2204/+806
| | | | | | | | | | | | | | | | | | 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
|
* Apply codegen with idiomatic lifetimesVeetaha2020-06-112-141/+141
|
* Separating parsing of `for` in predicates and typesMatthew Jasper2020-06-101-0/+2
|
* correctly infer labelled breaksrobojumper2020-05-311-0/+1
|
* Support raw_ref_op's raw reference operatorrobojumper2020-05-281-0/+3
|
* Remove an equals sign from `ConstArg` (this probably pertains only to ↵veetaha2020-05-121-1/+0
| | | | | | ConstParam) (As per matklad)
* Convert TODO to a Note(matklad)veetaha2020-05-121-0/+1
|
* Convert to TODOs to FIXMEs as per matkladveetaha2020-05-121-4/+2
|
* Revert "Remove MacroStmts as per edwin0cheng" (cc @edwin0cheng) and add a ↵veetaha2020-05-121-0/+32
| | | | | | | | | | fixme to document it. This reverts commit 7a49165f5d5c8186edd04f874eae8a98e39d3df6. MacroStmts ast node is not used by itself, but it pertains to SyntaxNodeKind MACRO_STMTS that is used by ra_paser, so even tho the node itself is not used, it is better to keep it with a FIXME to actually add a doc comment when it becomes useful.
* Add a doc comment on the difference between Name and NameRef ast nodesveetaha2020-05-121-1/+16
|
* Resolve TODO about macro 2.0 defveetaha2020-05-101-6/+4
|
* Fix typoveetaha2020-05-101-1/+1
|
* Carify on a semicolon in macro callveetaha2020-05-101-1/+6
|
* Resolve TODO about curly-braced constructions in expression statementveetaha2020-05-101-1/+3
|
* Resolve todos about refs and empty statementsveetaha2020-05-101-4/+4
|
* Converted TODO about MacroItems to FIXME as per edwin0chengveetaha2020-05-101-6/+2
|
* Verified ConstArg example, waiting for response on what `=` sign pertains toveetaha2020-05-101-1/+1
|
* Correcy use tree and type args docsveetaha2020-05-101-3/+3
|
* Correct `use` cannot have type args as per flodieboldveetaha2020-05-101-1/+1
|
* Correct path docs and add colon2 token to Path ast nodeveetaha2020-05-101-8/+14
|
* Add example with const in TypeBound as per flodieboldveetaha2020-05-101-1/+1
|
* Properly document const impl as per flodieboldveetaha2020-05-101-2/+2
|
* Remove MacroStmts as per edwin0chengveetaha2020-05-101-32/+0
|
* Add proper docs for TokenTree as per edwin0chengveetaha2020-05-101-1/+2
|
* Run codegen of ast types with documentationveetaha2020-05-101-138/+1345
|
* Rename ImplItem to AssocItemEdwin Cheng2020-05-051-18/+18
|
* Add documents owner for ImplDef and SourceFileEdwin Cheng2020-05-031-0/+2
|
* Introduce EffectExprAleksey Kladov2020-05-021-49/+25
|
* Revert "Merge #4233"Aleksey Kladov2020-05-021-2/+35
| | | | | This reverts commit a5f2b16366f027ad60c58266a66eb7fbdcbda9f9, reversing changes made to c96b2180c1c4206a0a98c280b4d30897eb116336.
* Merge #4246bors[bot]2020-05-011-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4246: Validate uses of self and super r=matklad a=djrenren This change follows on the validation of the `crate` keyword in paths. It verifies the following things: `super`: - May only be preceded by other `super` segments - If in a `UseItem` then all semantically preceding paths also consist only of `super` `self` - May only be the start of a path Just a note, a couple times while working on this I found myself really wanting a Visitor of some sort so that I could traverse descendants while skipping sub-trees that are unimportant. Iterators don't really work for this, so as you can see I reached for recursion. Considering paths are generally small a fancy debounced visitor probably isn't important but figured I'd say something in case we had something like this lying around and I wasn't using it. Co-authored-by: John Renner <[email protected]>
| * Validate uses of self and superJohn Renner2020-05-011-0/+2
| |
* | Remove dead code, which elaborately pretends to be aliveAleksey Kladov2020-04-301-35/+2
|/
* Fix a bunch of false-positives in join-linesAleksey Kladov2020-04-301-0/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 19:11:49 +0000