Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | make typing infra slightly more extensible | Aleksey Kladov | 2019-10-25 | 1 | -6/+2 |
| | |||||
* | for highlighting, search only the current file | Aleksey Kladov | 2019-10-24 | 1 | -3/+8 |
| | |||||
* | add couple of profiling calls | Aleksey Kladov | 2019-10-23 | 1 | -0/+4 |
| | |||||
* | fix highlighting | Ekaterina Babshukova | 2019-10-22 | 1 | -0/+1 |
| | |||||
* | restructure a bit | Ekaterina Babshukova | 2019-10-22 | 1 | -1/+1 |
| | |||||
* | make `handle_references` accept refs from other files | Ekaterina Babshukova | 2019-10-22 | 1 | -4/+9 |
| | |||||
* | fixup folding ranges for "lineFoldingOnly" clients #2033 | Alex Zatelepin | 2019-10-21 | 1 | -2/+8 |
| | |||||
* | Added test for check doc strings in crates. | Alexander Andreev | 2019-09-30 | 3 | -0/+6 |
| | | | | #1856 | ||||
* | move fold conversino to conv.rs | Aleksey Kladov | 2019-09-19 | 1 | -32/+6 |
| | |||||
* | fix typo | Aleksey Kladov | 2019-09-19 | 1 | -1/+1 |
| | |||||
* | fix renaming of modules | Aleksey Kladov | 2019-09-05 | 1 | -8/+6 |
| | |||||
* | cleanup main loop | Aleksey Kladov | 2019-08-31 | 1 | -1/+1 |
| | |||||
* | move lsp-server to a separate repository | Aleksey Kladov | 2019-08-30 | 2 | -10/+11 |
| | |||||
* | translate \n -> \r\n on the way out | Aleksey Kladov | 2019-08-20 | 1 | -2/+4 |
| | |||||
* | update lsp | Aleksey Kladov | 2019-08-17 | 1 | -2/+1 |
| | |||||
* | Drop support for old extendSelection API | Aleksey Kladov | 2019-08-12 | 1 | -22/+1 |
| | | | | | | Emacs now handles this via native LSP request https://github.com/emacs-lsp/lsp-mode/commit/dc86bbb227147aa8141e690ad5648fdbd2ebdb9f | ||||
* | Always set the runnable name | Kirill Bulatov | 2019-08-09 | 1 | -11/+11 |
| | |||||
* | Extract common logic | Kirill Bulatov | 2019-08-09 | 1 | -55/+42 |
| | |||||
* | Show backtraces in lens runnables | Kirill Bulatov | 2019-08-09 | 1 | -1/+5 |
| | |||||
* | Merge #1652 | bors[bot] | 2019-08-06 | 1 | -8/+1 |
|\ | | | | | | | | | | | | | | | | | | | | | | | 1652: Improve type hints behavior r=matklad a=SomeoneToIgnore This PR fixed the following type hints issues: * Restructures the `InlayKind` enum contents based on the discussion here: https://github.com/rust-analyzer/rust-analyzer/pull/1606#issuecomment-515968055 * Races described in #1639 * Caches the latest decorations received for each file to show them the next time the file is opened (instead of a new server request) Co-authored-by: Kirill Bulatov <[email protected]> | ||||
| * | Use proper inlay kinds | Kirill Bulatov | 2019-08-04 | 1 | -8/+1 |
| | | |||||
* | | use Conv for severity | Aleksey Kladov | 2019-08-06 | 1 | -15/+6 |
|/ | |||||
* | remove-comment | kjeremy | 2019-07-31 | 1 | -1/+0 |
| | |||||
* | Hide comments in rust section of doc comments | Roman Stoliar | 2019-07-30 | 1 | -1/+1 |
| | |||||
* | Support destructuring patterns | Kirill Bulatov | 2019-07-28 | 1 | -0/+3 |
| | |||||
* | Improve inlay hinting for types | Kirill Bulatov | 2019-07-26 | 1 | -0/+3 |
| | | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code. | ||||
* | Make Analysis api cancellable | Kirill Bulatov | 2019-07-25 | 1 | -29/+35 |
| | |||||
* | Code review fixes | Kirill Bulatov | 2019-07-22 | 1 | -1/+22 |
| | |||||
* | Do not show the lens with type hints | Kirill Bulatov | 2019-07-21 | 1 | -13/+4 |
| | |||||
* | Resolve types on the server | Kirill Bulatov | 2019-07-21 | 1 | -25/+10 |
| | |||||
* | Refactor server api | Kirill Bulatov | 2019-07-20 | 1 | -28/+42 |
| | |||||
* | If possible, show type lenses for the let bindings | Kirill Bulatov | 2019-07-20 | 1 | -16/+26 |
| | |||||
* | Add "Run" lens for binary runnables | Kirill Bulatov | 2019-07-16 | 1 | -1/+1 |
| | |||||
* | simplify | Aleksey Kladov | 2019-07-08 | 1 | -23/+7 |
| | |||||
* | add try_conv_with_to_vec | Aleksey Kladov | 2019-07-08 | 1 | -19/+8 |
| | |||||
* | Simplify responses by using into() | Jeremy Kolb | 2019-07-07 | 1 | -11/+12 |
| | |||||
* | use flatten branch of lsp-types | Jeremy Kolb | 2019-07-07 | 1 | -23/+12 |
| | |||||
* | Formatting again | Jeremy Kolb | 2019-07-05 | 1 | -5/+5 |
| | |||||
* | Symplify by using into() | Jeremy Kolb | 2019-07-05 | 1 | -3/+3 |
| | |||||
* | Fix formatting | Jeremy Kolb | 2019-07-04 | 1 | -5/+5 |
| | |||||
* | Change default() | Jeremy Kolb | 2019-07-04 | 1 | -1/+1 |
| | |||||
* | Update to lsp-types 0.58.0 | Jeremy Kolb | 2019-07-04 | 1 | -5/+5 |
| | |||||
* | allow rustfmt to reorder imports | Aleksey Kladov | 2019-07-04 | 1 | -11/+10 |
| | | | | | | This wasn't a right decision in the first place, the feature flag was broken in the last rustfmt release, and syntax highlighting of imports is more important anyway | ||||
* | Swallow expected `rustfmt` errors | Ryan Cumming | 2019-06-26 | 1 | -10/+25 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | My workflow in Visual Studio Code + Rust Analyzer has become: 1. Make a change to Rust source code using all the analysis magic 2. Save the file to trigger `cargo watch`. I have format on save enabled for all file types so this also runs `rustfmt` 3. Fix any diagnostics that `cargo watch` finds Unfortunately if the Rust source has any syntax errors the act of saving will pop up a scary "command has failed" message and will switch to the "Output" tab to show the `rustfmt` error and exit code. I did a quick survey of what other Language Servers do in this case. Both the JSON and TypeScript servers will swallow the error and return success. This is consistent with how I remember my workflow in those languages. The syntax error will show up as a diagnostic so it should be clear why the file isn't formatting. I checked the `rustfmt` source code and while it does distinguish "parse errors" from "operational errors" internally they both result in exit status of 1. However, more catastrophic errors (missing `rustfmt`, SIGSEGV, etc) will return 127+ error codes which we can distinguish from a normal failure. This changes our handler to log an info message and feign success if `rustfmt` exits with status 1. Another option I considered was only swallowing the error if the formatting request came from format-on-save. However, the Language Server Protocol doesn't seem to distinguish those cases. | ||||
* | rename | Aleksey Kladov | 2019-06-01 | 1 | -33/+33 |
| | |||||
* | move completed requests to a separate file | Aleksey Kladov | 2019-05-31 | 3 | -11/+81 |
| | |||||
* | less noisy status | Aleksey Kladov | 2019-05-29 | 1 | -1/+1 |
| | |||||
* | add latest requests to status page | Aleksey Kladov | 2019-05-29 | 1 | -2/+10 |
| | |||||
* | rename stray id field | Pascal Hertleif | 2019-05-27 | 1 | -1/+1 |
| | |||||
* | make it build again | Pascal Hertleif | 2019-05-27 | 1 | -1/+1 |
| |