Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | | Update tests for or-patterns | Matthew Jasper | 2020-02-09 | 4 | -60/+184 | |
| | | ||||||
* | | Add or- and parenthesized-patterns | Matthew Jasper | 2020-02-09 | 1 | -6/+75 | |
| | | ||||||
* | | Some README fixes/cleanups | Florian Diebold | 2020-02-09 | 1 | -1/+1 | |
| | | | | | | | | Make capitalization more consistent and fix some typos. | |||||
* | | Rename add import assist | Kirill Bulatov | 2020-02-07 | 1 | -1/+1 | |
|/ | ||||||
* | Merge #3047 | bors[bot] | 2020-02-07 | 4 | -11/+11 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | 3047: Update async unsafe fn ordering in parser r=matklad a=kiljacken As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: `async unsafe fn` and not `unsafe async fn`. This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering. Fixes #3025 Co-authored-by: Emil Lauridsen <[email protected]> | |||||
| * | Update async unsafe fn ordering. | Emil Lauridsen | 2020-02-07 | 4 | -11/+11 | |
| | | | | | | | | | | | | | | | | | | | | As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: `async unsafe fn` and not `unsafe async fn`. This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering. Fixes #3025 | |||||
* | | Merge #3040 | bors[bot] | 2020-02-07 | 14 | -200/+608 | |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3040: Rework value parameter parsing r=matklad a=tobz1000 Fixes #2847. - `Fn__(...)` parameters with idents/patterns no longer parse - Trait function parameters with arbitrary patterns parse - Trait function parameters without idents/patterns no longer parse - `fn(...)` parameters no longer parse with patterns other than a single ident __Question__: The pre-existing test `param_list_opt_patterns` has been kept as-is, although the name no longer makes sense (it's testing `Fn__(...)` params, which aren't allowed patterns any more). What would be best to do about this? Co-authored-by: Toby Dimmick <[email protected]> | |||||
| * | | Closure params test | Toby Dimmick | 2020-02-06 | 2 | -0/+73 | |
| | | | ||||||
| * | | Rework value parameter parsing | Toby Dimmick | 2020-02-06 | 12 | -200/+535 | |
| | | | | | | | | | | | | | | | | | | | | | - `Fn__(...)` parameters with idents/patterns no longer parse - Trait function parameters with arbitrary patterns parse - Trait function parameters without idents/patterns no longer parse - `fn(...)` parameters no longer parse with patterns other than a single ident | |||||
* | | | Cleanup early return assist | Aleksey Kladov | 2020-02-07 | 1 | -8/+21 | |
| | | | ||||||
* | | | Generalize invert_if to just always work | Aleksey Kladov | 2020-02-07 | 1 | -1/+5 | |
| |/ |/| | ||||||
* | | A tiny bit more consistent API | Aleksey Kladov | 2020-02-06 | 1 | -1/+1 | |
|/ | ||||||
* | Refactor if-let -> match assist to use ast::make | Aleksey Kladov | 2020-02-05 | 2 | -3/+25 | |
| | ||||||
* | Make sure that newly created nodes are the root of the tree | Aleksey Kladov | 2020-02-04 | 1 | -2/+11 | |
| | ||||||
* | ra_syntax: added tests for tokenization errors | Veetaha | 2020-02-03 | 150 | -49/+427 | |
| | ||||||
* | ra_syntax: add backticks around tokens specimen | Veetaha | 2020-02-03 | 1 | -12/+23 | |
| | ||||||
* | ra_syntax: removed unnecessary init statement from reparsing tests | Veetaha | 2020-02-03 | 1 | -3/+0 | |
| | ||||||
* | ra_syntax: rename first_token() -> lex_first_token() | Veetaha | 2020-02-03 | 1 | -3/+3 | |
| | ||||||
* | ra_syntax: fixed a typo in doc comment | Veetaha | 2020-02-03 | 1 | -2/+4 | |
| | ||||||
* | ra_syntax: refactored the lexer design as per @matklad and @kiljacken PR review | Veetaha | 2020-02-03 | 7 | -173/+193 | |
| | ||||||
* | ra_syntax: remove backticks from TokenizeError message since that is not ↵ | Veetaha | 2020-02-03 | 1 | -9/+9 | |
| | | | | Markdown ;( | |||||
* | add better docs for tokenize errors | Veetaha | 2020-02-03 | 1 | -2/+2 | |
| | ||||||
* | ra_syntax: moved ParsedToken derive attribute under the doc comment | Veetaha | 2020-02-03 | 1 | -1/+1 | |
| | ||||||
* | ra_syntax: fixed doc comment | Veetaha | 2020-02-03 | 1 | -1/+1 | |
| | ||||||
* | Reimplemented lexer with vectors instead of iterators | Veetaha | 2020-02-03 | 8 | -187/+241 | |
| | ||||||
* | ra_syntax: changed added diagnostics information returned from tokenize() ↵ | Veetaha | 2020-02-03 | 4 | -74/+237 | |
| | | | | (implemented with iterators) | |||||
* | Fixed a typo | Veetaha | 2020-01-22 | 1 | -1/+1 | |
| | ||||||
* | Fixed a typo | Veetaha | 2020-01-22 | 1 | -1/+1 | |
| | ||||||
* | Preserved a comment on the bug previously present in ast::Literal::kind() | Veetaha | 2020-01-22 | 1 | -0/+5 | |
| | ||||||
* | ra_syntax: remove code duplication and token reevaluation from ↵ | Veetaha | 2020-01-22 | 1 | -30/+20 | |
| | | | | ast::Literal::kind() | |||||
* | changed 'descendants()' to 'children()' | TomasKralCZ | 2020-01-20 | 1 | -4/+1 | |
| | ||||||
* | added eq_token() method to LetStmt | TomasKralCZ | 2020-01-19 | 1 | -0/+7 | |
| | ||||||
* | Nest attrs into exprs in function args | Aleksey Kladov | 2020-01-17 | 2 | -28/+22 | |
| | ||||||
* | Extract expr_with_attrs | Aleksey Kladov | 2020-01-17 | 1 | -10/+14 | |
| | ||||||
* | Merge pull request #2813 from jyn514/arg_attributes | Aleksey Kladov | 2020-01-17 | 2 | -0/+40 | |
|\ | | | | | Allow attributes before function arguments | |||||
| * | move inline function closer to relevant code | Joshua Nelson | 2020-01-17 | 4 | -115/+40 | |
| | | | | | | | | also updates generated inline tests | |||||
| * | Allow attributes before function arguments | Joshua Nelson | 2020-01-12 | 2 | -0/+115 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for function calls of the form: ```rust ( #[attr(...)] 1.2, #[attr_one(...)] #[attr_two(...)] 1.5, ... etc ... ) ``` Closes https://github.com/rust-analyzer/rust-analyzer/issues/2801 | |||||
* | | Minimize test | Aleksey Kladov | 2020-01-16 | 6 | -116/+48 | |
| | | ||||||
* | | Simplify array parsing | Aleksey Kladov | 2020-01-16 | 1 | -20/+13 | |
| | | ||||||
* | | Merge #2827 | bors[bot] | 2020-01-16 | 2 | -28/+28 | |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2827: Fix array element attribute position r=matklad a=edwin0cheng This PR fixed a bug which an ATTR node insert in the wrong place in array element. ~~And introduce `precede_next` for allow outer attributes to insert into a parsed `expr`.~~ related #2783 Co-authored-by: Edwin Cheng <[email protected]> | |||||
| * | | Fix array element attribute position | Edwin Cheng | 2020-01-16 | 2 | -28/+28 | |
| | | | ||||||
* | | | Merge #2837 | bors[bot] | 2020-01-15 | 1 | -0/+3980 | |
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2837: Accidentally quadratic r=matklad a=matklad Our syntax highlighting is accdentally quadratic. Current state of the PR fixes it in a pretty crude way, looks like for the proper fix we need to redo how source-analyzer works. **NB:** don't be scared by diff stats, that's mostly a test-data file Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | | | Add a test | Aleksey Kladov | 2020-01-15 | 1 | -0/+3980 | |
| |/ / | ||||||
* | | | More orthogonal path editing | Aleksey Kladov | 2020-01-15 | 2 | -16/+44 | |
| | | | ||||||
* | | | More fluent API | Aleksey Kladov | 2020-01-15 | 1 | -10/+12 | |
| | | | ||||||
* | | | Slightly more fluent API | Aleksey Kladov | 2020-01-15 | 2 | -14/+14 | |
| | | | ||||||
* | | | Simplify | Aleksey Kladov | 2020-01-15 | 1 | -5/+8 | |
| | | | ||||||
* | | | Simplify | Aleksey Kladov | 2020-01-15 | 1 | -7/+5 | |
|/ / | ||||||
* | | refactor(ra_syntax.validation): removed code duplication from ↵ | Veetaha | 2020-01-14 | 1 | -35/+26 | |
| | | | | | | | | validate_literal() function | |||||
* | | Some clippy lints | kjeremy | 2020-01-13 | 1 | -2/+2 | |
|/ |