aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* fix block parse problembravomikekilo2019-08-031-7/+6
|
* remove-commentkjeremy2019-07-311-1/+0
|
* Add explicit newline preserving testskjeremy2019-07-312-0/+23
|
* Update insta to 0.9.0 and cargo updatekjeremy2019-07-312-2/+2
|
* Merge #1627bors[bot]2019-07-313-5/+27
|\ | | | | | | | | | | | | | | 1627: Hide ignored lines in rustdoc r=kjeremy a=rizakrko This fixes #1620. Co-authored-by: Roman Stoliar <[email protected]>
| * Fixed review commentsRoman Stoliar2019-07-301-3/+9
| |
| * Hide comments in rust section of doc commentsRoman Stoliar2019-07-303-5/+21
| |
* | rustfmtEvgenii P2019-07-301-10/+15
| |
* | Fix flip comma assistEvgenii P2019-07-301-0/+25
| |
* | Add merge_match_arm assist, bump rowan to 0.6.1Phil Ellison2019-07-293-1/+191
| |
* | 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
| | |
* | | Fixed request changes.Alexander Andreev2019-07-291-9/+19
| | |
* | | Added resolve modules inside inline moduleAlexander Andreev2019-07-292-54/+147
|/ / | | | | | | #1510
* | it's a good idea to build extension before installing itAleksey Kladov2019-07-271-1/+7
| |
* | Overhaul installation processAleksey Kladov2019-07-272-44/+114
| | | | | | | | | | | | | | The new commands are $ cargo install-ra --client-code $ cargo install-ra --server --jemalloc
* | 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.
* | Make Analysis api cancellableKirill Bulatov2019-07-258-87/+107
| |
* | move syntax tests to unit testsAleksey Kladov2019-07-24511-12/+11
| |
* | Merge #1584bors[bot]2019-07-243-526/+88
|\ \ | | | | | | | | | | | | | | | | | | | | | 1584: switch to upstream unescape r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | switch to upstream unescapeAleksey Kladov2019-07-243-526/+88
| | |
* | | Merge #1583bors[bot]2019-07-241-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | 1583: :arrow_up: rowan r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | :arrow_up: rowanAleksey Kladov2019-07-241-1/+1
| |/
* | Merge #1573bors[bot]2019-07-243-6/+69
|\ \ | |/ |/| | | | | | | | | | | 1573: fix: parse box syntax inside parentheses r=matklad a=csmoe r? @matklad Co-authored-by: csmoe <[email protected]>
| * fix: parse box syntax inside parenthesescsmoe2019-07-223-6/+69
| |
* | show local variable types in completionEkaterina Babshukova2019-07-236-9/+30
| |
* | Merge #1549bors[bot]2019-07-235-1/+237
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1549: Show type lenses for the resolved let bindings r=matklad a=SomeoneToIgnore Types that are fully unresolved are not displayed: <img width="279" alt="image" src="https://user-images.githubusercontent.com/2690773/61518122-8e4ba980-aa11-11e9-9249-6d9f9b202e6a.png"> A few concerns that I have about the current implementation: * I've adjusted the `file_structure` API method to return the information about the `let` bindings. Although it works fine, I have a feeling that adding a new API method would be the better way. But this requires some prior discussion, so I've decided to go for an easy way with an MVP. Would be nice to hear your suggestions. * There's a hardcoded `{undersolved}` check that I was forced to use, since the method that resolves types returns a `String`. Is there a better typed API I can use? This will help, for instance, to add an action to the type lenses that will allow us to navigate to the type. Co-authored-by: Kirill Bulatov <[email protected]>
| * | Code review fixesKirill Bulatov2019-07-224-30/+70
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-01 08:53:54 +0000