aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix flip comma assistEvgenii P2019-07-301-0/+25
|
* Merge #1602bors[bot]2019-07-294-4/+194
|\ | | | | | | | | | | | | | | 1602: Assist to merge identical match arms r=matklad a=theotherphil Fixes https://github.com/rust-analyzer/rust-analyzer/issues/1250 Co-authored-by: Phil Ellison <[email protected]>
| * Add merge_match_arm assist, bump rowan to 0.6.1Phil Ellison2019-07-294-4/+194
|/
* Merge #1604bors[bot]2019-07-292-14/+34
|\ | | | | | | | | | | | | | | 1604: Fix failing type interference for floating point literal r=matklad a=theotherphil Fixes https://github.com/rust-analyzer/rust-analyzer/issues/1592 Co-authored-by: Phil Ellison <[email protected]>
| * Move assist test, add literal type inference testPhil Ellison2019-07-292-26/+15
| |
| * cargo formatPhil Ellison2019-07-281-3/+1
| |
| * Add special case for f32 and f43 suffices on Literal.kindPhil Ellison2019-07-283-17/+26
| |
| * Add issue link and trailing newlinePhil Ellison2019-07-281-1/+2
| |
| * More direct failing testPhil Ellison2019-07-281-0/+13
| |
| * Add failing testPhil Ellison2019-07-281-0/+10
| |
* | Merge #1601bors[bot]2019-07-2938-1064/+870
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 1601: Inline snapshots for tests r=matklad a=theotherphil Fixes https://github.com/rust-analyzer/rust-analyzer/issues/1127. The "cargo format" commits are required to get the formatting tests to pass. However, they actually mess up the formatting. Co-authored-by: Phil Ellison <[email protected]>
| * | Rerun cargo format, to make tests pass and formatting incorrectPhil Ellison2019-07-282-7/+7
| | |
| * | Remove vertical ellipses in references.csPhil Ellison2019-07-281-34/+33
| | |
| * | Remove vertical ellipses from tests in complete_snippet.rs and presentation.rsPhil Ellison2019-07-282-102/+94
| | |
| * | Remove vertical ellipses from tests in complete_scope.rsPhil Ellison2019-07-281-243/+225
| | |
| * | cargo formatPhil Ellison2019-07-285-117/+117
| | |
| * | Inline snapshot for test_file_structure (less clear that this one is a good ↵Phil Ellison2019-07-282-192/+187
| | | | | | | | | | | | idea)
| * | Inline snapshots for all tests in runnables.rsPhil Ellison2019-07-285-88/+68
| | |
| * | Inline snapshots for all tests in references.rsPhil Ellison2019-07-282-39/+33
| | |
| * | Inline snapshots for all tests in complete_snippet, remove now-unused ↵Phil Ellison2019-07-287-81/+58
| | | | | | | | | | | | check_completion
| * | Inline snapshots for all tests in presentation.rsPhil Ellison2019-07-287-177/+152
| | |
| * | Inline snapshots for all tests in complete_scope.rsPhil Ellison2019-07-2814-434/+396
| | |
| * | Remove unused highlights_code_inside_macro snapshot, inline ↵Phil Ellison2019-07-283-83/+33
| |/ | | | | | | rename_mod_in_dir snapshot
* | Merge #1621bors[bot]2019-07-292-10/+23
|\ \ | | | | | | | | | | | | | | | | | | | | | 1621: Document AssistBuilder r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | Document AssistBuilderAleksey Kladov2019-07-292-10/+23
| | | | | | | | | | | | closes #1603
* | | Merge #1606bors[bot]2019-07-293-47/+311
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1606: Add `if let`, `while let` and match arm inlay hints r=matklad a=SomeoneToIgnore <img width="693" alt="image" src="https://user-images.githubusercontent.com/2690773/62013363-152f1d80-b19a-11e9-90ea-07568757baa2.png"> Add more inline hints support. Looks like `while let` type inference support is missing currently, so the corresponding hint tests lack the actual results. I've also could not find a good way to distinguish between `a` and `b` pats in the following expressions: `if let Some(Test { a: None, b: y }) = &test {};` In this case we don't need to add a hint for first pat (`a: None`), since it's matched against the particular enum variant and need a hint for `y`, since it's a new variable. But both `a` and `b` are `BIND_PAT` with similar contents, so looks like there's nothing I can check for to find any differences. I don't display any hints for such cases now, to avoid confusion, but would be nice to know if there's a way to fix this behavior. Co-authored-by: Kirill Bulatov <[email protected]>
| * | Support destructuring patternsKirill Bulatov2019-07-283-47/+311
| | |
* | | Merge #1605bors[bot]2019-07-292-49/+152
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1605: Resolve modules inside inline module r=matklad a=andreevlex #1510 Co-authored-by: Alexander Andreev <[email protected]>
| * | | Fixed request changes.Alexander Andreev2019-07-291-9/+19
| | | |
| * | | Added resolve modules inside inline moduleAlexander Andreev2019-07-292-54/+147
| |/ / | | | | | | | | | #1510
* | | Merge #1617bors[bot]2019-07-292-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1617: document upgrade process r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | document upgrade processAleksey Kladov2019-07-292-0/+5
| | | | | | | | | | | | | | | | closes #1615
* | | | Merge #1614bors[bot]2019-07-291-1/+1
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 1614: show prettier diff on CI r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | show prettier diff on CIAleksey Kladov2019-07-291-1/+1
| | | |
* | | | Merge #1610bors[bot]2019-07-291-6/+11
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1610: Ignore cancelled inlay hints responses r=matklad a=SomeoneToIgnore Fixes #1607 Co-authored-by: Kirill Bulatov <[email protected]>
| * | | | Style fixesKirill Bulatov2019-07-291-1/+4
| | | | |
| * | | | Ignore cancelled inlay hints responsesKirill Bulatov2019-07-291-6/+8
| | |/ / | |/| |
* | | | Merge #1613bors[bot]2019-07-292-110/+99
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | 1613: :arrow_up: npm r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | :arrow_up: npmAleksey Kladov2019-07-292-110/+99
| |/ /
* | | Merge #1611bors[bot]2019-07-291-2/+1
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1611: install npm deps once r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | install npm deps onceAleksey Kladov2019-07-291-2/+1
|/ /
* | Merge #1599bors[bot]2019-07-271-1/+7
|\ \ | | | | | | | | | | | | | | | | | | | | | 1599: it's a good idea to build extension before installing it r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | it's a good idea to build extension before installing itAleksey Kladov2019-07-271-1/+7
|/ /
* | Merge #1597bors[bot]2019-07-276-58/+128
|\ \ | | | | | | | | | | | | | | | | | | | | | 1597: Overhaul installation process r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | Overhaul installation processAleksey Kladov2019-07-276-58/+128
|/ / | | | | | | | | | | | | The new commands are $ cargo install-ra --client-code $ cargo install-ra --server --jemalloc
* | Merge #1596bors[bot]2019-07-272-4/+40
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1596: Implement inlay hints for emacs r=matklad a=flodiebold I wanted to have the nice type hints in emacs as well :smile: ![2019-07-27-111718_982x171_scrot](https://user-images.githubusercontent.com/906069/61992560-43104700-b060-11e9-879f-8ad60f71b2e5.png) Co-authored-by: Florian Diebold <[email protected]>
| * | Implement inlay hints for emacsFlorian Diebold2019-07-272-4/+40
|/ /
* | Merge #1594bors[bot]2019-07-263-61/+125
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1594: Improve inlay hinting for types r=matklad a=SomeoneToIgnore Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code. ![image](https://user-images.githubusercontent.com/2690773/61957524-2294ae00-afc8-11e9-8bdc-f86f9c84ab7e.png) Co-authored-by: Kirill Bulatov <[email protected]>
| * | Improve inlay hinting for typesKirill Bulatov2019-07-263-61/+125
|/ / | | | | | | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code.
* | Merge #1586bors[bot]2019-07-255-1/+150
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1586: Add type decorators r=matklad a=SomeoneToIgnore A follow-up of https://github.com/rust-analyzer/rust-analyzer/pull/1549 Now the frontend shows inlay hints as VS Code Decorators: <img width="666" alt="image" src="https://user-images.githubusercontent.com/2690773/61802687-918fcc80-ae39-11e9-97b0-3195ab467393.png"> <img width="893" alt="image" src="https://user-images.githubusercontent.com/2690773/61802688-93599000-ae39-11e9-8bcb-4512e22aa3ed.png"> A few notes on the implementation: * I could not find a normal way to run and display the hints for the file that's already open in the VS Code when it starts. The updating code runs ok, but does not actually show anything. Seems like I miss some event that I could add a handler to. I've also experimented with `setTimeout` and it worked, but this is too ugly. The hints appear now when a new file is open or when some change is done in the existing file. * If there's a `dbg!` used in the lsp_server, the frontend starts receiving change events that contain the string from the `dbg!` output. It should not be the case in a real life, but I've decided to cover this case, just in case. * For bigger files, ~500 lines, the decorators start to blink, when updated, this does not seem to be very much of a problem for me at this particular stage of the feature development and can be optimized later. In the worst case, those decorators can be turned off in settings. * Cursor movement is rather non-intuitive on the right edge of the decorator. Seems like a thing to fix in the VS Code, not in the plugin. Co-authored-by: Kirill Bulatov <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 22:19:18 +0000