Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | 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 | |
| | ||||||
* | Semantic highlighting spike | Pascal Hertleif | 2019-05-27 | 1 | -1/+5 | |
| | | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request? | |||||
* | add profile calls to real-time requests | Aleksey Kladov | 2019-05-27 | 1 | -0/+5 | |
| | ||||||
* | Basic resolution for ADT | kjeremy | 2019-04-23 | 1 | -0/+20 | |
| | ||||||
* | switch to official extend selection API | Aleksey Kladov | 2019-04-21 | 1 | -1/+46 | |
| | ||||||
* | add a couple of profiling points | Aleksey Kladov | 2019-04-14 | 1 | -0/+3 | |
| | ||||||
* | Sends cwd info for runnables and code lenses | Roberto Vidal | 2019-04-14 | 1 | -0/+5 | |
| | ||||||
* | Refactor CallInfo function signatures to new FunctionSignature type | Ville Penttinen | 2019-04-09 | 1 | -18/+5 | |
| | | | | | This is used by CallInfo to create a pretty printed function signature that can be used with completions and other places as well. | |||||
* | Add optional range parameter to SyntaxTreeParams | Ville Penttinen | 2019-03-03 | 1 | -1/+3 | |
| | | | | | When range is provided, instead of showing the syntax for the whole file, we'll show the syntax tree for the given range. | |||||
* | Add new type HoverResult to contain the results of hovering | Ville Penttinen | 2019-02-26 | 1 | -1/+1 | |
| | | | | | This makes testing hovers easier as well as allows us to do more things with the results if needed. | |||||
* | Assign IDs to assists | Aleksey Kladov | 2019-02-24 | 1 | -9/+39 | |
| | ||||||
* | Update lsp-types and backtrace | kjeremy | 2019-02-21 | 1 | -1/+1 | |
| | ||||||
* | Refactor find_all_refs to return ReferenceSearchResult | Ville Penttinen | 2019-02-17 | 1 | -10/+28 | |
| | ||||||
* | Add support for container_name in workspace/symbol query | Ville Penttinen | 2019-02-12 | 1 | -1/+1 | |
| | ||||||
* | reformat the world | Aleksey Kladov | 2019-02-08 | 2 | -62/+17 | |
| | ||||||
* | Some clippy cleanups | kjeremy | 2019-02-06 | 1 | -19/+15 | |
| | ||||||
* | Fill deprecation for LSP | kjeremy | 2019-02-05 | 1 | -1/+1 | |
| | ||||||
* | Move comment | kjeremy | 2019-02-04 | 1 | -12/+13 | |
| | ||||||
* | Future proof by explicitly matching against None | kjeremy | 2019-02-04 | 1 | -1/+1 | |
| |