Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | simplify | Lukas Wirth | 2021-06-17 | 2 | -2/+2 |
| | |||||
* | clippy::redudant_borrow | Maan2003 | 2021-06-13 | 1 | -3/+3 |
| | |||||
* | Update test fixtures | Laurențiu Nicola | 2021-05-24 | 10 | -0/+56 |
| | |||||
* | Code review feedback. | James Leitch | 2021-04-21 | 1 | -4/+6 |
| | |||||
* | Diagnostic Remap Path Prefixes added. | James Leitch | 2021-04-21 | 1 | -35/+32 |
| | |||||
* | Diagnostic paths attempt to use VSCode's path join behavior before ↵ | James Leitch | 2021-04-21 | 1 | -3/+30 |
| | | | | defaulting to Rust's path join behavior. | ||||
* | Prevent being able to rename items that are not part of the workspace | Lukas Wirth | 2021-04-18 | 6 | -0/+6 |
| | |||||
* | Check for and skip dummy macro files | Jonas Schievink | 2021-04-01 | 2 | -120/+16 |
| | |||||
* | Adjust message when pointing at location in macro | Jonas Schievink | 2021-04-01 | 1 | -2/+10 |
| | |||||
* | Search for a suitable primary location | Jonas Schievink | 2021-03-31 | 1 | -9/+27 |
| | |||||
* | Rename `convert_location` -> `location` | Jonas Schievink | 2021-03-31 | 1 | -11/+11 |
| | |||||
* | Improve rustc diagnostic mapping | Jonas Schievink | 2021-03-30 | 3 | -49/+272 |
| | |||||
* | don't clone types that are copy (clippy::clone_on_copy) | Matthias Krüger | 2021-03-17 | 1 | -1/+1 |
| | |||||
* | Bump cargo_metadata | Laurențiu Nicola | 2021-03-02 | 1 | -1/+1 |
| | |||||
* | Update tests | Jeremy Kolb | 2021-02-20 | 10 | -0/+104 |
| | |||||
* | Update Test Data | Christopher Serr | 2021-02-01 | 1 | -1/+46 |
| | |||||
* | Don't filter code suggestions on Applicability | Christopher Serr | 2021-02-01 | 1 | -4/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've noticed that there are various suggestions that rust-analyzer seems to filter out, even if they make sense. Here's an example of where it seems like there should be a suggestion, but there isn't: ![https://i.imgur.com/wsjM6iz.png](https://i.imgur.com/wsjM6iz.png) It turns out that this specific suggestion is not considered `MachineApplicable`, which are the only suggestions that rust-analyzer accepts. However if you read the documentation for `MachineApplicable`, https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L27-L29 then you realize that these are specifically only those suggestions that rust-analyzer could even automatically apply (in some distant future, behind some setting or so). Other suggestions that may have some semantic impact do not use `MachineApplicable`. So all other suggestions are still intended to be suggested to the user, just not automatically applied without the user being consulted. https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L22-L24 So with that in mind, rust-analyzer should almost definitely not filter out `MaybeIncorrect` (which honestly is named horribly, it just means that it's a semantic change, not just a syntactical one). Then there's `HasPlaceholders` which basically is just another semantic one, but with placeholders. The user will have to make some adjustments, but the suggestion still is perfectly valid. rust-analyzer could probably detect those placeholders and put proper "tab through" markers there for the IDE, but that's not necessary for now. Then the last one is `Unspecified` which is so unknown that I don't even know how to judge it, meaning that the suggestion should probably also just be suggested to the user and then they can decide. So with all that in mind, I'm proposing to get rid of the check for Applicability entirely. | ||||
* | Don't duplicate rustc diagnostics fixes | Jonas Schievink | 2021-01-15 | 5 | -282/+32 |
| | |||||
* | Filter out empty rustc spans | Jonas Schievink | 2020-12-21 | 1 | -0/+4 |
| | |||||
* | Apply suggestions from code review | Jonas Schievink | 2020-12-06 | 2 | -2/+2 |
| | | | Co-authored-by: Laurențiu Nicola <[email protected]> | ||||
* | Update expect tests | Jonas Schievink | 2020-12-06 | 7 | -46/+977 |
| | |||||
* | Emit additional diagnostics for hints/help/etc | Jonas Schievink | 2020-12-06 | 1 | -73/+116 |
| | |||||
* | update diagnostics test_data with code_description changes | Lukas Wirth | 2020-11-18 | 6 | -6/+108 |
| | |||||
* | Link clippy lint codes in diagnostics | Lukas Wirth | 2020-11-18 | 1 | -7/+22 |
| | |||||
* | Link rustc error codes in diagnostics | Lukas Wirth | 2020-11-18 | 1 | -3/+19 |
| | |||||
* | Latest LSP 3.16 protocol | kjeremy | 2020-11-16 | 1 | -2/+2 |
| | | | | Pulls in https://github.com/gluon-lang/lsp-types/pull/186 | ||||
* | Update tests | Aleksey Kladov | 2020-11-12 | 10 | -21/+168 |
| | |||||
* | Switch to upstream protocol for resolving code action | Aleksey Kladov | 2020-11-10 | 5 | -5/+5 |
| | | | | | | Note that we have to maintain custom implementation on the client side: I don't see how to marry bulitin resolve support with groups and snippets. | ||||
* | Update tests | Jeremy A. Kolb | 2020-10-26 | 10 | -0/+22 |
| | |||||
* | Latest proposed LSP 3.16.0 | kjeremy | 2020-10-26 | 1 | -0/+4 |
| | | | | Needs: https://github.com/gluon-lang/lsp-types/pull/183 | ||||
* | Highlight errors in macros | Igor Aleksanov | 2020-09-06 | 2 | -7/+89 |
| | |||||
* | :arrow_up: expect-test | Aleksey Kladov | 2020-08-28 | 11 | -10/+595 |
| | |||||
* | Switch to expect_test from crates.io | Aleksey Kladov | 2020-08-21 | 1 | -1/+1 |
| | |||||
* | Align diagnostics config with the rest of rust-analyzer | Aleksey Kladov | 2020-08-18 | 1 | -9/+9 |
| | |||||
* | Rename ra_hir_def -> hir_def | Aleksey Kladov | 2020-08-13 | 1 | -6/+6 |
| | |||||
* | Mark machine applicable fixes as preferred | Jeremy Kolb | 2020-07-16 | 1 | -0/+1 |
| | | | | | | | This allows us to run the auto fix command from vscode to automatically fix all diagnostics in the file. They are also distinguished in the UI. | ||||
* | Update lsp-types to account for new CodeActionKind structure | Jeremy Kolb | 2020-07-11 | 1 | -1/+1 |
| | |||||
* | Make sure there are no commands in code actions | Aleksey Kladov | 2020-07-11 | 1 | -1/+0 |
| | |||||
* | Always put config first | Aleksey Kladov | 2020-07-09 | 1 | -1/+0 |
| | |||||
* | Move diagnostics tests to expect | Aleksey Kladov | 2020-07-09 | 11 | -680/+49 |
| | |||||
* | Simplify | Aleksey Kladov | 2020-07-09 | 11 | -132/+12 |
| | |||||
* | Cleanup diagnostic conversion code | Aleksey Kladov | 2020-07-09 | 1 | -102/+71 |
| | |||||
* | Cleanup | Aleksey Kladov | 2020-06-26 | 1 | -3/+3 |
| | |||||
* | Rename ra_flycheck -> flycheck | Aleksey Kladov | 2020-06-25 | 1 | -9/+10 |
| | |||||
* | Warnings as hint or info | Gabriel Valfridsson | 2020-06-16 | 3 | -13/+372 |
| | |||||
* | Merge #4867 | bors[bot] | 2020-06-13 | 1 | -69/+4 |
|\ | | | | | | | | | | | | | | | | | | | | | 4867: Cleanup URL handling r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | Cleanup URL handling | Aleksey Kladov | 2020-06-13 | 1 | -69/+4 |
| | | |||||
* | | Revert "Hide squiggly for unused and unnecessary" | Gabriel Valfridsson | 2020-06-12 | 2 | -3/+2 |
|/ | | | | This reverts commit 599c105e6fabb2b81c2d0a11b86c0c96f6ab1b88. | ||||
* | Merge branch 'master' into compute-lazy-assits | Mikhail Rakhmanov | 2020-06-03 | 2 | -2/+3 |
|\ | | | | | | | | | | | # Conflicts: # crates/rust-analyzer/src/main_loop/handlers.rs # crates/rust-analyzer/src/to_proto.rs | ||||
| * | Hide squiggly for unused and unnecessary | Gabriel Valfridsson | 2020-06-03 | 2 | -2/+3 |
| | |