Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Merge #3034 | bors[bot] | 2020-02-06 | 1 | -1/+1 | |
|\ | | | | | | | | | | | | | | | 3034: Remove ImportLocator hack r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | Make assists use ImportsLocator directly | Aleksey Kladov | 2020-02-06 | 1 | -1/+1 | |
| | | ||||||
* | | Update indexmap and bstr | kjeremy | 2020-02-06 | 1 | -4/+4 | |
|/ | ||||||
* | Merge #3029 | bors[bot] | 2020-02-06 | 1 | -0/+31 | |
|\ | | | | | | | | | | | | | | | 3029: Docs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | Move to a crate | Aleksey Kladov | 2020-02-06 | 1 | -0/+31 | |
| | | ||||||
* | | Add profiling around add_impl_members | Aleksey Kladov | 2020-02-06 | 1 | -0/+1 | |
|/ | | | | | | | | | This intention is pretty slow for `impl Interator`, because it has a ton of default methods which need to be substituted. The proper fix here is to not compute the actual edit until the user triggers the action, but that's awkward to do in the LSP right now, so let's just put a profiling code for now. | |||||
* | Update aho-corasick (removes unsafety) and serde_json | kjeremy | 2020-02-04 | 1 | -4/+4 | |
| | ||||||
* | Update regex | kjeremy | 2020-02-01 | 1 | -4/+4 | |
| | ||||||
* | Switch Cargo.lock to the new format | Aleksey Kladov | 2020-01-30 | 1 | -696/+688 | |
| | ||||||
* | Update crates | Jeremy Kolb | 2020-01-30 | 1 | -20/+20 | |
| | ||||||
* | Upgrade Chalk | Florian Diebold | 2020-01-27 | 1 | -28/+28 | |
| | ||||||
* | Update insta | kjeremy | 2020-01-27 | 1 | -17/+6 | |
| | ||||||
* | Update crates | Jeremy Kolb | 2020-01-26 | 1 | -22/+22 | |
| | ||||||
* | Bump main thread priority on windows | Aleksey Kladov | 2020-01-26 | 1 | -0/+1 | |
| | ||||||
* | Disable env_logger humantime feature | Aleksey Kladov | 2020-01-25 | 1 | -10/+0 | |
| | | | | | We rarely care about timings of events, and, when we care, we need millisecond precision | |||||
* | Update crates | kjeremy | 2020-01-22 | 1 | -39/+39 | |
| | ||||||
* | Crates up | kjeremy | 2020-01-16 | 1 | -12/+12 | |
| | ||||||
* | Merge #2837 | bors[bot] | 2020-01-15 | 1 | -6/+6 | |
|\ | | | | | | | | | | | | | | | | | | | 2837: Accidentally quadratic r=matklad a=matklad Our syntax highlighting is accdentally quadratic. Current state of the PR fixes it in a pretty crude way, looks like for the proper fix we need to redo how source-analyzer works. **NB:** don't be scared by diff stats, that's mostly a test-data file Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | :arrow_up: once_cell | Aleksey Kladov | 2020-01-15 | 1 | -6/+6 | |
| | | ||||||
* | | itertools::Either -> either::Either | Kirill Bulatov | 2020-01-15 | 1 | -2/+2 | |
| | | ||||||
* | | Apply the api design suggestions | Kirill Bulatov | 2020-01-15 | 1 | -0/+1 | |
|/ | ||||||
* | lsp-types 0.69.0 | Jeremy Kolb | 2020-01-15 | 1 | -4/+4 | |
| | | | | Stabilizes most proposed features | |||||
* | Update backtrace | kjeremy | 2020-01-13 | 1 | -3/+3 | |
| | ||||||
* | Update crates | Jeremy Kolb | 2020-01-12 | 1 | -49/+55 | |
| | ||||||
* | Use FxHashMap | Florian Diebold | 2020-01-11 | 1 | -0/+1 | |
| | ||||||
* | :arrow_up: rowan | Aleksey Kladov | 2020-01-09 | 1 | -3/+3 | |
| | ||||||
* | Implement proposed CallHierarchy feature | Jeremy Kolb | 2020-01-08 | 1 | -0/+1 | |
| | | | | See: https://github.com/microsoft/vscode-languageserver-node/blob/master/protocol/src/protocol.callHierarchy.proposed.ts | |||||
* | :arrow_up: pico-args | Aleksey Kladov | 2020-01-08 | 1 | -4/+4 | |
| | ||||||
* | :arrow_up: crates | Aleksey Kladov | 2020-01-07 | 1 | -22/+21 | |
| | ||||||
* | Crates up | Jeremy Kolb | 2020-01-06 | 1 | -17/+18 | |
| | ||||||
* | Merge #2743 | bors[bot] | 2020-01-03 | 1 | -22/+0 | |
|\ | | | | | | | | | | | | | | | 2743: Switch ast declaration from ron to a macro r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | Switch ast declaration from ron to a macro | Aleksey Kladov | 2020-01-03 | 1 | -22/+0 | |
| | | ||||||
* | | Update quick-error | kjeremy | 2020-01-03 | 1 | -4/+4 | |
|/ | ||||||
* | Update dependencies | Jeremy Kolb | 2020-01-01 | 1 | -23/+23 | |
| | ||||||
* | :arrow_up: lsp-server | Aleksey Kladov | 2019-12-31 | 1 | -3/+3 | |
| | ||||||
* | Merge #2668 | bors[bot] | 2019-12-29 | 1 | -0/+15 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2668: In-server cargo check watching r=matklad a=kiljacken Opening a draft now so people can follow the progress, and comment if they spot something stupid. Things that need doing: - [x] Running cargo check on save - [x] Pipe through configuration options from client - [x] Tests for parsing behavior - [x] Remove existing cargo watch support from VSCode extension - [x] Progress notification in VSCode extension using LSP 3.15 `$/progress` notification - [ ] ~~Rework ra-ide diagnostics to support secondary messages~~ - [ ] ~~Make cargo-check watcher use ra-ide diagnostics~~ ~~I'd love some input on whether to try to keep the status bar progress thingy for VSCode? It will require some plumbing, and maintaining yet another rust-analyzer specific LSP notification, which I'm not sure we want to.~~ Fixes #1894 Co-authored-by: Emil Lauridsen <[email protected]> | |||||
| * | Move cargo watch functionality to separate crate | Emil Lauridsen | 2019-12-27 | 1 | -2/+15 | |
| | | ||||||
| * | Migrate tests from extension to rust | Emil Lauridsen | 2019-12-25 | 1 | -0/+1 | |
| | | ||||||
| * | Initial implementation of cargo check watching | Emil Lauridsen | 2019-12-25 | 1 | -0/+1 | |
| | | ||||||
* | | anyhow and crossbeam-queue | Jeremy Kolb | 2019-12-27 | 1 | -7/+8 | |
|/ | ||||||
* | Update lsp-types and rayon | Jeremy Kolb | 2019-12-23 | 1 | -9/+9 | |
| | ||||||
* | lsp-types 0.67 | Jeremy Kolb | 2019-12-23 | 1 | -3/+10 | |
| | ||||||
* | Merge #2636 | bors[bot] | 2019-12-23 | 1 | -28/+28 | |
|\ | | | | | | | | | | | | | | | 2636: Chalk update and refactoring r=flodiebold a=flodiebold This updates the Chalk integration to https://github.com/rust-lang/chalk/pull/311, which will presumably get merged soon, and refactors it some more, most notably introducing our own `TypeFamily` instead of reusing `ChalkIr`. It's still mostly the same as `ChalkIr` though, except for using Salsa `InternId`s directly. Co-authored-by: Florian Diebold <[email protected]> | |||||
| * | Update Chalk, clean up Chalk integration a bit | Florian Diebold | 2019-12-22 | 1 | -28/+28 | |
| | | ||||||
* | | Bump lsp-types to 0.66.0 (fixes #2651) | John-John Tedro | 2019-12-23 | 1 | -3/+3 | |
|/ | ||||||
* | Optimize and profile | Aleksey Kladov | 2019-12-21 | 1 | -0/+1 | |
| | ||||||
* | Update crates | Jeremy Kolb | 2019-12-21 | 1 | -9/+9 | |
| | ||||||
* | Use SelectionRange from LSP 3.15 | Jeremy Kolb | 2019-12-20 | 1 | -3/+3 | |
| | ||||||
* | Add local functions to bodies | Aleksey Kladov | 2019-12-20 | 1 | -0/+1 | |
| | ||||||
* | :arrow_up: deps | Aleksey Kladov | 2019-12-19 | 1 | -24/+24 | |
| |