aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/test_data/parser/inline
Commit message (Collapse)AuthorAgeFilesLines
* Update testsAleksey Kladov2020-07-301-1/+1
|
* Update testsAleksey Kladov2020-07-301-4/+4
|
* Update testsAleksey Kladov2020-07-3021-25/+25
|
* Fix panic in split and merge import assistsLaurențiu Nicola2020-06-232-0/+16
|
* Update parser tests with env varAleksey Kladov2020-06-151-1/+0
|
* Add example of old trait object syntaxMatthew Jasper2020-06-112-1/+38
|
* Move complex inline test to own fileMatthew Jasper2020-06-112-267/+1
|
* Separating parsing of `for` in predicates and typesMatthew Jasper2020-06-104-273/+372
|
* Correctly parse <_> paths in patternsAleksey Kladov2020-06-092-0/+39
| | | | closes #3659
* Parse default unsafe fnAvi Dessauer2020-06-082-0/+43
|
* Move default const test out of lineAvi Dessauer2020-06-044-90/+0
|
* Update testsAvi Dessauer2020-06-046-0/+109
|
* Parse default unsafe & default constAvi Dessauer2020-06-041-14/+20
|
* Support raw_ref_op's raw reference operatorrobojumper2020-05-282-44/+134
|
* Fix parsing of blocks without `{`Aleksey Kladov2020-05-022-24/+0
|
* Cleanup inline testsAleksey Kladov2020-05-028-30/+59
|
* Update test dataAleksey Kladov2020-05-02110-5120/+4929
|
* Merge #4227bors[bot]2020-04-302-25/+26
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4227: Report invalid, nested, multi-segment crate-paths r=matklad a=djrenren There was a bug in the previous path-validating code that didn't detect multi-segment paths that started with `crate`. ```rust // Successfully reported use foo::{crate}; // BUG: was not being reported use foo::{crate::bar}; ``` This was due to my confusion about path-associativity. That is, the path with no qualifier is the innermost path, not the outermost. I've updated the code with a lot of comments to explain what's going on. This bug was discovered when I found an erroneous `ok` test which I reported here: https://github.com/rust-analyzer/rust-analyzer/issues/4226 This test now fails and has been modified, hopefully in the spirit of the original test, to be correct. Sorry about submitting the bug in the first place! Co-authored-by: John Renner <[email protected]>
| * Report invalid, nested, multi-segment crate-pathsJohn Renner2020-04-302-25/+26
| | | | | | | | | | | | | | | | | | | | Specifically, things like: use foo::{crate::bar}; Are now being caught, when before we only caught: use foo::{crate};
* | Special-case try macro_rulesEdwin Cheng2020-04-302-0/+28
|/
* Special-case try macro to better support 2015 editionAleksey Kladov2020-04-302-0/+36
|
* Convert tests to text-sizeAleksey Kladov2020-04-25172-10327/+10327
|
* Align grammar for record patterns and literalsAleksey Kladov2020-04-113-21/+25
| | | | | | The grammar now looks like this [name_ref :] pat
* Make records grammar more orthogonalAleksey Kladov2020-04-113-4/+62
| | | | | | | | | | | | We used name [: expr] grammar before, now it is [name :] expr which makes things simpler
* Rename some tokensAleksey Kladov2020-04-10120-405/+405
|
* Migrate tests .txt -> .rastveetaha2020-04-06171-0/+0
| | | | | | | | The sytax tree output files now use .rast extension (rust-analyzer syntax tree or rust abstract syntax tree (whatever)). This format has a editors/code/ra_syntax_tree.tmGrammar.json declaration that supplies nice syntax highlighting for .rast files.
* Macro patterns are not confused with expressions.Aleksey Kladov2020-04-031-10/+11
| | | | | | | | | | | We treat macro calls as expressions (there's appropriate Into impl), which causes problem if there's expresison and non-expression macro in the same node (like in the match arm). We fix this problem by nesting macor patterns into another node (the same way we nest path into PathExpr or PathPat). Ideally, we probably should add a similar nesting for macro expressions, but that needs some careful thinking about macros in blocks: `{ am_i_expression!() }`.
* Fix parsing lambdas with return typeAleksey Kladov2020-03-252-0/+46
| | | | | | | We should eat only a single block, and not whatever larger expression may start with a block. closes #3721
* Support arbitrary discriminantsAleksey Kladov2020-03-202-0/+31
| | | | Closes #3661
* Parse variadics correctlyAleksey Kladov2020-03-132-2/+4
| | | | closes #3571
* Move verbose tests out of lineAleksey Kladov2020-03-138-387/+45
|
* Fix parsing of stement-ish binary expressionsAleksey Kladov2020-03-112-0/+41
| | | | closes #3512
* Rename ast::ImplBlock -> ast::ImplDefAleksey Kladov2020-02-2917-20/+20
|
* Parse attr in rhs of let stmtsEdwin Cheng2020-02-282-7/+35
|
* ra_syntax: migrate test data to 0-length text-range of SyntaxError when ↵Veetaha2020-02-1712-34/+34
| | | | constructed from TextUnit
* ra_syntax: reshape SyntaxError for the sake of removing redundancyVeetaha2020-02-1711-32/+32
|
* Run cargo testHan Mertens2020-02-121-0/+26
|
* Run cargo xtask codegenHan Mertens2020-02-121-0/+1
|
* Address review commentsMatthew Jasper2020-02-102-7/+58
|
* Update tests for or-patternsMatthew Jasper2020-02-094-60/+184
|
* Merge #3047bors[bot]2020-02-074-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 Lauridsen2020-02-074-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
* | Closure params testToby Dimmick2020-02-062-0/+73
| |
* | Rework value parameter parsingToby Dimmick2020-02-0610-103/+474
|/ | | | | | | - `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
* Nest attrs into exprs in function argsAleksey Kladov2020-01-171-10/+10
|
* Merge pull request #2813 from jyn514/arg_attributesAleksey Kladov2020-01-172-0/+40
|\ | | | | Allow attributes before function arguments
| * move inline function closer to relevant codeJoshua Nelson2020-01-174-115/+40
| | | | | | | | also updates generated inline tests
| * Allow attributes before function argumentsJoshua Nelson2020-01-122-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 testAleksey Kladov2020-01-166-116/+48
| |
* | Fix array element attribute positionEdwin Cheng2020-01-162-28/+28
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 06:10:59 +0000