Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Rename TypeParamList -> GenericParamList | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Rename TypeAliasDef -> TypeAlias | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Rename FnDef -> Fn | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Rename UseItem -> Use | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Finish extern crates grammar | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Rename Rename | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Split ItemList & AssocItemList | Aleksey Kladov | 2020-07-30 | 1 | -0/+1 |
| | |||||
* | Switch to ungrammar from ast_src | Aleksey Kladov | 2020-07-29 | 1 | -1979/+5 |
| | | | | | | | | | | | | | | | | | | 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 code | Aleksey Kladov | 2020-07-29 | 1 | -8/+0 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-07-29 | 1 | -1/+0 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-07-29 | 1 | -8/+0 |
| | |||||
* | Owned AST IR | Aleksey Kladov | 2020-07-29 | 1 | -1911/+1919 |
| | |||||
* | Separating parsing of `for` in predicates and types | Matthew Jasper | 2020-06-10 | 1 | -1/+1 |
| | |||||
* | correctly infer labelled breaks | robojumper | 2020-05-31 | 1 | -1/+1 |
| | |||||
* | Support raw_ref_op's raw reference operator | robojumper | 2020-05-28 | 1 | -1/+3 |
| | |||||
* | Convert TODO about ParamList used in closures to a FIXME | veetaha | 2020-05-12 | 1 | -2/+1 |
| | | | | cc @matklad (you didn't comment on this one) | ||||
* | Remove an equals sign from `ConstArg` (this probably pertains only to ↵ | veetaha | 2020-05-12 | 1 | -3/+1 |
| | | | | | | ConstParam) (As per matklad) | ||||
* | Remove a comment on NameRefToken as per matklad | veetaha | 2020-05-12 | 1 | -1/+1 |
| | |||||
* | Convert TODO to a FIXME as per matklad | veetaha | 2020-05-12 | 1 | -1/+1 |
| | |||||
* | Convert TODO to a Note(matklad) | veetaha | 2020-05-12 | 1 | -1/+1 |
| | |||||
* | Convert to TODOs to FIXMEs as per matklad | veetaha | 2020-05-12 | 1 | -4/+2 |
| | |||||
* | Revert "Remove MacroStmts as per edwin0cheng" (cc @edwin0cheng) and add a ↵ | veetaha | 2020-05-12 | 1 | -0/+13 |
| | | | | | | | | | | 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 nodes | veetaha | 2020-05-12 | 1 | -1/+16 |
| | |||||
* | Resolve TODO about macro 2.0 def | veetaha | 2020-05-10 | 1 | -8/+4 |
| | |||||
* | Fix typo | veetaha | 2020-05-10 | 1 | -1/+1 |
| | |||||
* | Carify on a semicolon in macro call | veetaha | 2020-05-10 | 1 | -2/+7 |
| | |||||
* | Resolve TODO about curly-braced constructions in expression statement | veetaha | 2020-05-10 | 1 | -1/+3 |
| | |||||
* | Remove TODO about Block since it was removed | veetaha | 2020-05-10 | 1 | -3/+3 |
| | |||||
* | Resolve todos about refs and empty statements | veetaha | 2020-05-10 | 1 | -5/+4 |
| | |||||
* | Converted TODO about MacroItems to FIXME as per edwin0cheng | veetaha | 2020-05-10 | 1 | -8/+3 |
| | |||||
* | Verified ConstArg example, waiting for response on what `=` sign pertains to | veetaha | 2020-05-10 | 1 | -4/+3 |
| | |||||
* | Correcy use tree and type args docs | veetaha | 2020-05-10 | 1 | -5/+3 |
| | |||||
* | Correct `use` cannot have type args as per flodiebold | veetaha | 2020-05-10 | 1 | -1/+1 |
| | |||||
* | Correct path docs and add colon2 token to Path ast node | veetaha | 2020-05-10 | 1 | -12/+14 |
| | |||||
* | Add example with const in TypeBound as per flodiebold | veetaha | 2020-05-10 | 1 | -4/+2 |
| | |||||
* | Remove todo comment about arg vs param difference as per clarification from ↵ | veetaha | 2020-05-10 | 1 | -4/+0 |
| | | | | flodiebold | ||||
* | Properly document const impl as per flodiebold | veetaha | 2020-05-10 | 1 | -2/+2 |
| | |||||
* | Remove on TypeAliasDef as per flodiebold | veetaha | 2020-05-10 | 1 | -2/+1 |
| | |||||
* | Remove MacroStmts as per edwin0cheng | veetaha | 2020-05-10 | 1 | -15/+0 |
| | |||||
* | Add proper docs for TokenTree as per edwin0cheng | veetaha | 2020-05-10 | 1 | -1/+2 |
| | |||||
* | Add ast docs to codegen script | veetaha | 2020-05-10 | 1 | -15/+1492 |
| | |||||
* | Rename ImplItem to AssocItem | Edwin Cheng | 2020-05-05 | 1 | -2/+2 |
| | |||||
* | Add documents owner for ImplDef and SourceFile | Edwin Cheng | 2020-05-03 | 1 | -2/+2 |
| | |||||
* | Introduce EffectExpr | Aleksey Kladov | 2020-05-02 | 1 | -12/+7 |
| | |||||
* | Revert "Merge #4233" | Aleksey Kladov | 2020-05-02 | 1 | -1/+4 |
| | | | | | This reverts commit a5f2b16366f027ad60c58266a66eb7fbdcbda9f9, reversing changes made to c96b2180c1c4206a0a98c280b4d30897eb116336. | ||||
* | Merge #4246 | bors[bot] | 2020-05-01 | 1 | -1/+1 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 super | John Renner | 2020-05-01 | 1 | -1/+1 |
| | | |||||
* | | Remove dead code, which elaborately pretends to be alive | Aleksey Kladov | 2020-04-30 | 1 | -4/+1 |
|/ | |||||
* | Fix a bunch of false-positives in join-lines | Aleksey Kladov | 2020-04-30 | 1 | -1/+1 |
| | |||||
* | Validate the location of `crate` in paths | John Renner | 2020-04-29 | 1 | -1/+1 |
| |