aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/tests
Commit message (Collapse)AuthorAgeFilesLines
...
* Add test for placeholder parameters in trait fn defsErlend Tobiassen2019-01-222-0/+35
|
* Update tests after allowing where predicate to accept typesErlend Tobiassen2019-01-224-20/+63
|
* Change parsing of struct field patternsMarcus Klaas de Vries2019-01-191-12/+10
|
* Finish move of StructField for pattern type inferenceMarcus Klaas de Vries2019-01-191-20/+26
|
* Fix handling of attributes in positional field listsDJMcNab2019-01-122-0/+43
|
* Fix handling of where clauses in tuple structsDJMcNab2019-01-102-0/+64
|
* switch ra_syntax to new rowan APIAleksey Kladov2019-01-081-4/+4
|
* Rename traits::impl_item -> impl_block as well, as well as the testsFlorian Diebold2019-01-044-0/+0
|
* Rename ImplItem to ImplBlockFlorian Diebold2019-01-0415-21/+20
| | | | | rustc uses the name ImplItem for items in impls, not the impl {} block itself, which could lead to confusion.
* add mod doc comment testcsmoe2019-01-042-0/+22
|
* Fix the same bug as #396 but for bytes tooDJMcNab2019-01-011-0/+1
|
* Fix the `panic` found whilst fuzzingDJMcNab2018-12-311-0/+1
|
* Merge #366bors[bot]2018-12-302-33/+46
|\ | | | | | | | | | | | | | | | | | | | | 366: parse minus before number literal pattern r=matklad a=csmoe r?@matklad ![unknown](https://user-images.githubusercontent.com/35686186/50547871-d5449e00-0c7d-11e9-9ff5-1031e78019de.png) Co-authored-by: csmoe <[email protected]>
| * parse minus before number literalcsmoe2018-12-302-33/+46
| |
* | Add fuzz failure to the fuzz-failures directoryDJMcNab2018-12-291-0/+1
|/
* fix suffix rangesAleksey Kladov2018-12-272-0/+79
|
* Improve parsing of incomplete field accesses in preparation for field completionFlorian Diebold2018-12-252-0/+38
| | | | | We need to be able to get the receiver even if there is no field name yet, and currently "a." wouldn't get parsed as a field name at all. This seems to help.
* CleanupFlorian Diebold2018-12-231-25/+31
|
* Add testing infrastructure for type inferenceFlorian Diebold2018-12-231-100/+5
| | | | - move dir_tests to test_utils for that.
* Remove TODO on self_hosting_parsingDJMcNab2018-12-211-8/+4
| | | | | | This improving this code is not a good use of people-time, and this might be the most performant approach nonwithstanding an api for this use case being added to walkdir
* Fix where clauses using fully qualified path syntaxDJMcNab2018-12-214-8/+133
|
* Add comment about the source of the weird_exprs testDJMcNab2018-12-212-2235/+2248
|
* Add weird_exprs testDJMcNab2018-12-202-0/+2385
|
* Run gen-testsDJMcNab2018-12-202-0/+59
|
* Fix the tests and fix the precommit hookDJMcNab2018-12-20246-547/+195
|
* Change parser tests dir to inline/ok and inline/errDJMcNab2018-12-201-2/+2
|
* Ensure that the parser tests pass or fail correctlyDJMcNab2018-12-201-8/+26
|
* Fix ambiguity with if breakDJMcNab2018-12-202-0/+71
| | | | Brought up by #290
* Add tests and only traverse in the crates directoryDJMcNab2018-12-195-92/+178
|
* Move is_block to lower in the call treeDJMcNab2018-12-192-61/+61
|
* Revert "Revert to f6f7c5"DJMcNab2018-12-191-3/+0
| | | | | | This approach is correct, but it needs an addition to Restrictions too This reverts commit ad00d0c8a5f64142e6636e8b048204c8f8982f4a.
* Revert to f6f7c5DJMcNab2018-12-191-0/+3
|
* Fix expression parsing by bailing out upon a macro block being foundDJMcNab2018-12-191-3/+0
| | | | | | TODO: Fix this when the block like macro is in expression position E.g. `test(test!{})` currently parses
* Fix parsing of inclusive ranges (#214)DJMcNab2018-12-194-33/+150
| | | | I'm not certain that this is correct, so extra eyes would be good
* Add a test to ensure that we can parse each fileDJMcNab2018-12-191-2/+43
| | | | Note that this has a non-spurious failure in ra_analysis/src/mock_analysis
* Fixed cast expression parsing in ra_syntax.Roland Ruckerbauer2018-12-172-6/+48
| | | | | | | | | | | | | | | | | | | | | | The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes all plus sign after path types as extra. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`.
* rename Edit to TextEdit and AtomEdit to AtomTextEditBernardo2018-12-111-19/+19
|
* Update use path testDJMcNab2018-12-052-74/+2
|
* Improve/add the use_item documentationDJMcNab2018-12-0510-0/+485
|
* rename ROOT -> SOURCE_FILEAleksey Kladov2018-11-07177-177/+177
|
* Rename File -> SourceFileNodeAleksey Kladov2018-11-071-2/+2
|
* grammar: fix where clause parsingAleksey Kladov2018-11-062-0/+30
| | | | closes #205
* grammar: for predicates in whereAleksey Kladov2018-11-052-0/+62
| | | | closes #191
* Cargo FormatJeremy A. Kolb2018-10-161-5/+4
| | | | Run `cargo fmt` and ignore generated files
* Parse crate paths in expressionsAleksey Kladov2018-10-152-0/+44
|
* Attach comments smartlyAleksey Kladov2018-10-082-6/+6
|
* Support leading pipe in match armsDaniel McNab2018-10-032-12/+56
|
* support 2018 pathsAleksey Kladov2018-09-292-0/+16
|
* generate testsuite for impl_typecsmoe2018-09-264-8/+89
|
* parse impl typecsmoe2018-09-252-47/+28
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-11 16:12:12 +0000