Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Finish extern crates grammar | Aleksey Kladov | 2020-07-30 | 1 | -62/+62 |
| | |||||
* | Update tests | Aleksey Kladov | 2020-07-30 | 1 | -2/+6 |
| | |||||
* | Rename Rename | Aleksey Kladov | 2020-07-30 | 3 | -10/+10 |
| | |||||
* | Finish Module grammar | Aleksey Kladov | 2020-07-30 | 1 | -0/+1 |
| | |||||
* | Split ItemList & AssocItemList | Aleksey Kladov | 2020-07-30 | 2 | -24/+56 |
| | |||||
* | Finish SourceFile grammar | Aleksey Kladov | 2020-07-29 | 1 | -1/+3 |
| | |||||
* | Rename ModuleItem -> Item | Aleksey Kladov | 2020-07-29 | 4 | -388/+388 |
| | |||||
* | Rename NomialDef -> AdtDef | Aleksey Kladov | 2020-07-29 | 1 | -19/+19 |
| | |||||
* | Switch to ungrammar from ast_src | Aleksey Kladov | 2020-07-29 | 3 | -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 code | Aleksey Kladov | 2020-07-29 | 1 | -41/+0 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-07-29 | 1 | -3/+1 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-07-29 | 1 | -46/+0 |
| | |||||
* | Rename modules | Aleksey Kladov | 2020-07-23 | 4 | -8/+9 |
| | |||||
* | Store macro invocation parameters as text instead of tt | Laurențiu Nicola | 2020-07-22 | 2 | -4/+4 |
| | |||||
* | Move remove_bounds to edit.rs | Jonas Schievink | 2020-07-14 | 2 | -13/+15 |
| | |||||
* | missing impl members: remove assoc. type bounds | Jonas Schievink | 2020-07-14 | 1 | -0/+13 |
| | |||||
* | Comment decorations | Aleksey Kladov | 2020-07-12 | 1 | -1/+4 |
| | | | | closes #4461 | ||||
* | Make slow test parallel | Aleksey Kladov | 2020-07-11 | 1 | -18/+29 |
| | |||||
* | Don't mess with cursor position when adding hashes | Aleksey Kladov | 2020-07-09 | 1 | -6/+11 |
| | |||||
* | Simplify | Aleksey Kladov | 2020-07-09 | 1 | -1/+2 |
| | |||||
* | Unify tests | Aleksey Kladov | 2020-07-09 | 1 | -34/+2 |
| | |||||
* | Clippy perf warnings | kjeremy | 2020-07-06 | 1 | -6/+2 |
| | | | | Removes redundant clones | ||||
* | Unify magic env var name | Aleksey Kladov | 2020-07-01 | 1 | -1/+1 |
| | |||||
* | Move parser specific tests utils to parser tests | Aleksey Kladov | 2020-07-01 | 1 | -1/+99 |
| | |||||
* | Update the rest of the tests | Aleksey Kladov | 2020-06-29 | 1 | -0/+4 |
| | |||||
* | Simlify with matches!() | Veetaha | 2020-06-28 | 3 | -16/+10 |
| | |||||
* | Bump rustc_lexer | Laurențiu Nicola | 2020-06-27 | 1 | -12/+12 |
| | |||||
* | Merge #4962 | bors[bot] | 2020-06-21 | 3 | -1/+132 |
|\ | | | | | | | | | | | | | | | 4962: Implement APIs for parsing expressions, types, paths, patterns and items r=davidlattimore a=davidlattimore Co-authored-by: David Lattimore <[email protected]> | ||||
| * | Implement APIs for parsing expressions, types, paths, patterns and items | David Lattimore | 2020-06-21 | 3 | -1/+132 |
| | | |||||
* | | Merge #4851 | bors[bot] | 2020-06-19 | 1 | -0/+4 |
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | 4851: Add quickfix to add a struct field r=TimoFreiberg a=TimoFreiberg Related to #4563 I created a quickfix for record literals first because the NoSuchField diagnostic was already there. To offer that quickfix for FieldExprs with unknown fields I'd need to add a new diagnostic (or create a `NoSuchField` diagnostic for those cases) I think it'd make sense to make this a snippet completion (to select the generated type), but this would require changing the `Analysis` API and I'd like some feedback before I touch that. Co-authored-by: Timo Freiberg <[email protected]> | ||||
| * | Add quickfix to add a struct field | Timo Freiberg | 2020-06-12 | 1 | -0/+4 |
| | | |||||
* | | Merge #4872 | bors[bot] | 2020-06-18 | 1 | -46/+43 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | 4872: Reduce the usage of bare subscript operator r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]> | ||||
| * | | Reduce the usage of bare subscript operator | Veetaha | 2020-06-14 | 1 | -46/+43 |
| |/ | |||||
* | | Merge #4878 | bors[bot] | 2020-06-16 | 1 | -0/+8 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | 4878: Make "Replace qualified name with use" replace *all* mentions of the path r=matklad a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/4836 Co-authored-by: Jonas Schievink <[email protected]> | ||||
| * | | Fix `rewrite_root` when there's only 1 replacement | Jonas Schievink | 2020-06-13 | 1 | -0/+8 |
| |/ | |||||
* / | Make ra_syntax::{SyntaxNodeChildren, SyntaxElementChildren} public. | David Lattimore | 2020-06-15 | 1 | -1/+2 |
|/ | | | | SyntaxNode::children and SyntaxNode::children_with_tokens return these types, but there's currently no way AFAIK to name them. | ||||
* | Merge #4855 | bors[bot] | 2020-06-12 | 2 | -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 lifetimes | Veetaha | 2020-06-11 | 2 | -141/+141 |
| | | |||||
* | | Simplify | Veetaha | 2020-06-12 | 1 | -5/+5 |
|/ | |||||
* | Separating parsing of `for` in predicates and types | Matthew Jasper | 2020-06-10 | 2 | -1/+7 |
| | |||||
* | Use correct indent when replacing with match | Aleksey Kladov | 2020-06-09 | 1 | -4/+9 |
| | |||||
* | Fix bug in lexer for format specifier where the `type` and `width` were not ↵ | Leander Tentrup | 2020-06-07 | 1 | -14/+23 |
| | | | | correctly distinguished | ||||
* | Enable hover and autocomplete docs on macro generated items | Aaron Loucks | 2020-06-03 | 1 | -2/+11 |
| | |||||
* | Merge #4658 | bors[bot] | 2020-06-02 | 1 | -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 tokenization | Roland Ruckerbauer | 2020-05-30 | 1 | -5/+0 |
| | | | | | | | | Fixed by just not handling closing curlybrace escaping. | ||||
* | | Simplify | veetaha | 2020-06-02 | 1 | -1/+1 |
| | | |||||
* | | Small refactor | veetaha | 2020-05-31 | 1 | -2/+2 |
| | | |||||
* | | correctly infer labelled breaks | robojumper | 2020-05-31 | 1 | -0/+1 |
|/ | |||||
* | Support raw_ref_op's raw reference operator | robojumper | 2020-05-28 | 1 | -0/+3 |
| | |||||
* | Some FIXMEs were outdated: | Julian Wollersberger | 2020-05-24 | 1 | -3/+1 |
| | | | | | | | * Done at line 243: "Add validation of `crate` keyword not appearing in the middle of the symbol path" * Already happened: "Remove validation of unterminated literals (it is already implemented in `tokenize()`)" * Happens in `unescape()`: "Add validation of character literal containing only a single char" * Missing: "raw string literals and raw byte string literals" |