aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax
Commit message (Collapse)AuthorAgeFilesLines
* Implement basic completion for fieldsFlorian Diebold2018-12-252-1/+5
|
* Improve parsing of incomplete field accesses in preparation for field completionFlorian Diebold2018-12-253-9/+45
| | | | | 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.
* Type field accessesFlorian Diebold2018-12-252-2/+10
|
* Add AST definitions for struct/variant fields etc.Florian Diebold2018-12-253-12/+256
| | | | Fixes #117
* Infer result of struct literals, and recurse into their child expressionsFlorian Diebold2018-12-252-6/+26
|
* Resolve paths to defs (functions currently) during type inferenceFlorian Diebold2018-12-232-2/+6
|
* Make let statements kind of workFlorian Diebold2018-12-232-0/+5
|
* 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.
* Parse integer / float typesFlorian Diebold2018-12-232-2/+6
|
* Add beginnings of type infrastructureFlorian Diebold2018-12-232-13/+45
|
* Merge #316bors[bot]2018-12-211-1/+1
|\ | | | | | | | | | | | | | | 316: Fix handling of nested self in paths r=matklad a=DJMcNab See https://github.com/rust-analyzer/rust-analyzer/issues/231#issuecomment-442449505. Co-authored-by: DJMcNab <[email protected]>
| * Fix handling of nested self in pathsDJMcNab2018-12-211-1/+1
| |
* | 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
* | Remove uneeded todo in lexerDJMcNab2018-12-211-1/+1
|/
* Fix where clauses using fully qualified path syntaxDJMcNab2018-12-215-9/+139
|
* show debug repr of literalsAleksey Kladov2018-12-214-4/+4
|
* Add comment about the source of the weird_exprs testDJMcNab2018-12-212-2235/+2248
|
* Add weird_exprs testDJMcNab2018-12-202-0/+2385
|
* Fix parsing of contextual_keyword unionDJMcNab2018-12-201-1/+1
|
* Run gen-testsDJMcNab2018-12-202-0/+59
|
* Use a better way of skipping SEMIsDJMcNab2018-12-201-6/+6
|
* Support a blank expression before a semicolonDJMcNab2018-12-201-0/+6
|
* Fix the tests and fix the precommit hookDJMcNab2018-12-20252-556/+204
|
* Fix missing DOTDOTEQsDJMcNab2018-12-201-3/+3
|
* Don't require a command before EQ in a where clauseDJMcNab2018-12-201-1/+1
|
* 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
|
* Simplify NO_BLOCK testingDJMcNab2018-12-202-11/+3
|
* Fix ambiguity with if breakDJMcNab2018-12-204-5/+92
| | | | Brought up by #290
* Add tests and only traverse in the crates directoryDJMcNab2018-12-197-94/+185
|
* Move is_block to lower in the call treeDJMcNab2018-12-194-115/+104
|
* Revert "Revert to f6f7c5"DJMcNab2018-12-193-22/+36
| | | | | | This approach is correct, but it needs an addition to Restrictions too This reverts commit ad00d0c8a5f64142e6636e8b048204c8f8982f4a.
* Fix handling of structs in match armsDJMcNab2018-12-191-1/+1
|
* Revert to f6f7c5DJMcNab2018-12-193-36/+22
|
* Fix expression parsing by bailing out upon a macro block being foundDJMcNab2018-12-192-17/+12
| | | | | | TODO: Fix this when the block like macro is in expression position E.g. `test(test!{})` currently parses
* Possibly fix #225DJMcNab2018-12-192-21/+40
|
* Actually fix at_ts doc comment (committed wrong file :P)DJMcNab2018-12-191-1/+1
|
* Fix at_ts doc commentDJMcNab2018-12-191-1/+1
|
* Fix parsing of inclusive ranges (#214)DJMcNab2018-12-196-37/+158
| | | | 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-174-15/+66
| | | | | | | | | | | | | | | | | | | | | | 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-113-31/+31
|
* extract AtomEdit and Edit into new ra_text_edit crateBernardo2018-12-105-30/+6
|
* grand module renameAleksey Kladov2018-12-0811-0/+0
|
* Add a better text for hover and stop duplicating work done in ↵DJMcNab2018-12-082-2/+0
| | | | approximatelly_resolve_symbol
* Clarify and correct comment about multi_byte_tokensDJMcNab2018-12-081-2/+2
|
* Use json comparison code from cargo for heavy testsFlorian Diebold2018-12-061-1/+1
|
* modernize even moreAleksey Kladov2018-12-062-8/+4
|
* modernize some filesAleksey Kladov2018-12-063-10/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 05:36:14 +0000