aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/ast
Commit message (Collapse)AuthorAgeFilesLines
...
* | 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
* Dead codeAleksey Kladov2020-07-291-41/+0
|
* Remove dead codeAleksey Kladov2020-07-291-3/+1
|
* Remove dead codeAleksey Kladov2020-07-291-46/+0
|
* Rename modulesAleksey Kladov2020-07-233-1/+2
|
* Move remove_bounds to edit.rsJonas Schievink2020-07-142-13/+15
|
* missing impl members: remove assoc. type boundsJonas Schievink2020-07-141-0/+13
|
* Don't mess with cursor position when adding hashesAleksey Kladov2020-07-091-6/+11
|
* Clippy perf warningskjeremy2020-07-061-6/+2
| | | | Removes redundant clones
* Simlify with matches!()Veetaha2020-06-282-12/+9
|
* Add quickfix to add a struct fieldTimo Freiberg2020-06-121-0/+4
|
* 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
|/
* Separating parsing of `for` in predicates and typesMatthew Jasper2020-06-101-0/+2
|
* Use correct indent when replacing with matchAleksey Kladov2020-06-091-4/+9
|
* Fix bug in lexer for format specifier where the `type` and `width` were not ↵Leander Tentrup2020-06-071-14/+23
| | | | correctly distinguished
* Enable hover and autocomplete docs on macro generated itemsAaron Loucks2020-06-031-2/+11
|
* Merge #4658bors[bot]2020-06-021-5/+0
|\ | | | | | | | | | | | | | | | | | | 4658: Fix problem with format string tokenization r=matklad a=ruabmbua Fixed by just not handling closing curlybrace escaping. Closes https://github.com/rust-analyzer/rust-analyzer/issues/4637 Co-authored-by: Roland Ruckerbauer <[email protected]>
| * Fix problem with format string tokenizationRoland Ruckerbauer2020-05-301-5/+0
| | | | | | | | Fixed by just not handling closing curlybrace escaping.
* | correctly infer labelled breaksrobojumper2020-05-311-0/+1
|/
* Support raw_ref_op's raw reference operatorrobojumper2020-05-281-0/+3
|
* Update to rustc_lexer version 660.Julian Wollersberger2020-05-241-2/+3
| | | | Change `unescape_*()` to `unescape_literal()`.
*-. Merge #4521 #4522bors[bot]2020-05-202-27/+53
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4521: Use snippets in add_function r=matklad a=matklad bors r+ 🤖 4522: Explain the purpose of `ast::make` module more clearly r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| | * Explain the purpose of `ast::make` module more clearlyAleksey Kladov2020-05-201-4/+7
| |/ |/|
| * Moderate cleanup of add_functionAleksey Kladov2020-05-202-23/+46
|/
* Change type_arg to type_ref funcFedor Sakharov2020-05-141-2/+2
|
* Correctly fill default type parametersFedor Sakharov2020-05-131-0/+4
|
* Merge #4083bors[bot]2020-05-131-138/+1366
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4083: Smol documentation for ast nodes r=matklad a=Veetaha There is a tremendous amount of TODOs to clarify the topics I am not certain about. Please @matklad, @edwin0cheng review carefully, I even left some mentions of your names in todos to put your attention where you most probably can give comments. In order to simplify the review, I separated the codegen (i.e. changes in `ast/generated/nodes.rs`) from `ast_src` changes (they in fact just duplicate one another) into two commits. Also, I had to hack a little bit to let the docs be generated as doc comments and not as doc attributes because it's easier to read them this way and IIRC we don't support hints for `#[doc = ""]` attributes for now... Closes #3682 Co-authored-by: veetaha <[email protected]>
| * 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
| |