Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Merge #3533 | bors[bot] | 2020-03-09 | 1 | -1/+1 |
|\ | | | | | | | | | | | | | | | 3533: Updates insta to 0.15.0 and bumps console to 0.10.0 r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]> | ||||
| * | Updates insta to 0.15.0 and bumps console to 0.10.0 | kjeremy | 2020-03-09 | 1 | -1/+1 |
| | | |||||
* | | Fix SelectionRange return type | kjeremy | 2020-03-09 | 1 | -1/+1 |
|/ | |||||
* | lsp-types 0.72 | kjeremy | 2020-03-02 | 1 | -1/+1 |
| | |||||
* | Remove unused dependencies | Shotaro Yamada | 2020-02-27 | 1 | -3/+0 |
| | |||||
* | Update lsp-types | kjeremy | 2020-02-26 | 1 | -1/+1 |
| | |||||
* | Update versions | Kirill Bulatov | 2020-02-18 | 1 | -6/+6 |
| | |||||
* | Parse cargo output a line at a time. | Emil Lauridsen | 2020-01-29 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | | | We previously used serde's stream deserializer to read json blobs from the cargo output. It has an issue though: If the deserializer encounters invalid input, it gets stuck reporting the same error again and again because it is unable to foward over the input until it reaches a new valid object. Reading a line at a time and manually deserializing fixes this issue, because cargo makes sure to only outpu one json blob per line, so should we encounter invalid input, we can just skip a line and continue. The main reason this would happen is stray printf-debugging in procedural macros, so we still report that an error occured, but we handle it gracefully now. Fixes #2935 | ||||
* | Update crates | Jeremy Kolb | 2020-01-26 | 1 | -1/+1 |
| | |||||
* | Update crates | kjeremy | 2020-01-22 | 1 | -1/+1 |
| | |||||
* | lsp-types 0.69.0 | Jeremy Kolb | 2020-01-15 | 1 | -1/+1 |
| | | | | Stabilizes most proposed features | ||||
* | Update dependencies | Jeremy Kolb | 2020-01-01 | 1 | -1/+1 |
| | |||||
* | Move cargo watch functionality to separate crate | Emil Lauridsen | 2019-12-27 | 1 | -0/+17 |