aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* implement vfs events handlingAleksey Kladov2018-12-207-43/+349
|
* add io::TaskAleksey Kladov2018-12-202-26/+34
|
* Add type aliasAleksey Kladov2018-12-202-4/+8
|
* vfs crate scaffoldAleksey Kladov2018-12-206-68/+89
|
* wipAleksey Kladov2018-12-206-167/+452
|
* Merge #294bors[bot]2018-12-194-8/+8
|\ | | | | | | | | | | | | | | 294: Bump languageserver-types to 0.53.0 to support LSP 3.14.0 r=matklad a=kjeremy See: https://microsoft.github.io/language-server-protocol/specification#version_3_14_0 Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Bump languageserver-types to 0.53.0 to support LSP 3.14.0Jeremy A. Kolb2018-12-194-8/+8
|/ | | | See: https://microsoft.github.io/language-server-protocol/specification#version_3_14_0
* Merge #273bors[bot]2018-12-1914-234/+496
|\ | | | | | | | | | | | | | | | | | | | | | | 273: Add a test to ensure that we can parse each file r=matklad a=DJMcNab Note that this has a non-spurious failure in ra_analysis/src/mock_analysis. Probably fixes #195. If my understanding is correct, fixes #214 and fixes #225. Co-authored-by: DJMcNab <[email protected]>
| * 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
| * Reload package-lock.jsonDJMcNab2018-12-191-72/+78
| |
| * 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
* | Merge #291bors[bot]2018-12-186-17/+21
|\ \ | | | | | | | | | | | | | | | | | | | | | 291: File module source does not depend on syntax r=matklad a=matklad Fixes this problem: https://github.com/rust-analyzer/rust-analyzer/pull/289#issuecomment-448398571 Co-authored-by: Aleksey Kladov <[email protected]>
| * | File module source does not depend on syntaxAleksey Kladov2018-12-186-17/+21
|/ /
* | Merge #289bors[bot]2018-12-182-8/+21
|\ \ | | | | | | | | | | | | | | | | | | | | | 289: WIP: fix accidently quadratic behavior r=matklad a=matklad we've recmoputed item map every time previously :man_facepalming: :man_facepalming: :man_facepalming: Co-authored-by: Aleksey Kladov <[email protected]>
| * | disable gc for nowAleksey Kladov2018-12-181-1/+5
| | |
| * | Gc syntax trees after every modificationAleksey Kladov2018-12-182-8/+17
|/ /
* | Work around a bugAleksey Kladov2018-12-181-4/+7
| | | | | | | | cc #288
* | Merge #286bors[bot]2018-12-189-46/+62
|\ \ | | | | | | | | | | | | | | | | | | | | | 286: move thread worker to a separate crate r=matklad a=matklad Going to tackle https://github.com/rust-analyzer/rust-analyzer/issues/243, this is a refactoring towards that goal Co-authored-by: Aleksey Kladov <[email protected]>
| * | move thread worker to a separate crateAleksey Kladov2018-12-189-46/+62
|/ /
* | Merge #284bors[bot]2018-12-181-5/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 284: By default, log only to stderr, and not to disk. r=matklad a=eminence This fixes a common problem when running under VS Code, the user doesn't have permissions to create a `log` directory in the CWD. The old behavior can be re-enabled by setting `RA_INTERNAL_MODE=1` Fixes #282 Co-authored-by: Andrew Chin <[email protected]>
| * By default, log only to stderr, and not to disk.Andrew Chin2018-12-171-5/+5
| | | | | | | | | | | | | | This fixes a common problem when running under VS Code, the user doesn't have permissions to create a `log` directory in the CWD. The old behavior can be re-enabled by setting RA_INTERNAL_MODE=1
* | Merge #283bors[bot]2018-12-171-18/+58
|\ \ | |/ |/| | | | | | | | | | | 283: Docs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * big pictureAleksey Kladov2018-12-171-1/+28
| |
| * docs about cancelationAleksey Kladov2018-12-171-0/+5
| |
| * update architecture.mdAleksey Kladov2018-12-171-19/+27
|/
* Merge #280bors[bot]2018-12-174-15/+66
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 280: Fixed cast expression parsing in ra_syntax. r=matklad a=ruabmbua Fixes #279 Related to https://github.com/rust-analyzer/rust-analyzer/pull/273 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 the plus sign after path types as extra type bounds. 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()`. Co-authored-by: Roland Ruckerbauer <[email protected]>
| * 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()`.
* fix installation on windowsAleksey Kladov2018-12-171-1/+2
|
* Merge #277bors[bot]2018-12-153-15/+15
|\ | | | | | | | | | | | | | | 277: use new clear-terminal feature r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * use new clear-terminal featureAleksey Kladov2018-12-153-15/+15
|/
* Merge #276bors[bot]2018-12-1221-110/+156
|\ | | | | | | | | | | | | | | | | | | 276: Extract and rename AtomEdit and Edit into ra_text_edit r=matklad a=vemoo As discused in #105 Co-authored-by: Bernardo <[email protected]>
| * rename Edit to TextEdit and AtomEdit to AtomTextEditBernardo2018-12-1111-87/+92
| |
| * extract AtomEdit and Edit into new ra_text_edit crateBernardo2018-12-1019-40/+81
|/
* Merge #275bors[bot]2018-12-101-8/+18
|\ | | | | | | | | | | | | | | 275: Update ARCHITECTURE.md r=matklad a=h-michael I am still not familiar with the code base, so mostly I quote crate's comments. Co-authored-by: Hirokazu Hata <[email protected]>
| * Update ARCHITECTURE.mdHirokazu Hata2018-12-101-8/+18
|/
* Merge #274bors[bot]2018-12-101-0/+1
|\ | | | | | | | | | | | | | | | | 274: Add crates/*/target to gitignore r=matklad a=h-michael I am using rls and rust-analyzer together. Rls creates cache in `crates/*/target`, so I would like to add it to gitignore as well. Co-authored-by: Hirokazu Hata <[email protected]>
| * Add crates/*/target to gitignoreHirokazu Hata2018-12-101-0/+1
|/
* Merge #272bors[bot]2018-12-091-2/+30
|\ | | | | | | | | | | | | | | 272: use \b as word boundary when expanding single word in comments r=matklad a=vemoo as discused in #266 Co-authored-by: Bernardo <[email protected]>
| * use \b as word boundaryBernardo2018-12-091-2/+30
|/
* Merge #271bors[bot]2018-12-095-15/+75
|\ | | | | | | | | | | | | | | | | | | 271: Implement format hook r=matklad a=DJMcNab Tentatively: fixes #155. However, this does add all changes in staged files, which might not be desirable. However, I think we can't solve that without explicit support in rustfmt for it, so it should be fine. Co-authored-by: DJMcNab <[email protected]>
| * Reimplement format-hook using a rust binaryDJMcNab2018-12-093-27/+52
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 14:18:39 +0000