Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bump rustc_lexer | Laurențiu Nicola | 2021-05-24 | 1 | -2/+2 |
| | |||||
* | Bump object | Laurențiu Nicola | 2021-05-24 | 1 | -9/+3 |
| | |||||
* | Bump misc deps | Laurențiu Nicola | 2021-05-24 | 1 | -39/+45 |
| | |||||
* | Bump chalk | Laurențiu Nicola | 2021-05-24 | 1 | -8/+8 |
| | |||||
* | Update notify and fst | kjeremy | 2021-05-17 | 1 | -7/+6 |
| | |||||
* | internal: remove one more immutable tree | Aleksey Kladov | 2021-05-14 | 1 | -2/+2 |
| | |||||
* | Allow viewing the crate graph in a webview | Jonas Schievink | 2021-05-11 | 1 | -0/+7 |
| | |||||
* | internal: expose cfg attrs from hir::Crate | Aleksey Kladov | 2021-05-07 | 1 | -0/+1 |
| | |||||
* | Switch from jemalloc to tikv-jemalloc | John Renner | 2021-05-07 | 1 | -34/+34 |
| | |||||
* | Update to rowan 0.13.0-pre.5 | Dawer | 2021-05-06 | 1 | -2/+2 |
| | |||||
* | Update salsa | Jonas Schievink | 2021-05-05 | 1 | -2/+2 |
| | |||||
* | Replace `memmap` to `memmap2` in `proc_macro_api` | memoryruins | 2021-05-04 | 1 | -11/+1 |
| | |||||
* | cargo update | Jeremy Kolb | 2021-05-02 | 1 | -36/+37 |
| | |||||
* | Return ServerNotInitialized according to the spec | Jeremy Kolb | 2021-04-27 | 1 | -2/+2 |
| | | | | | | | According to the spec we should return ServerNotInitialized if the server is waiting for an initialize request and something else comes in. Upgrading to lsp-server 0.5.1 will do this and retry until the initialize request comes in. Fixes #8581 | ||||
* | Update deps | Jeremy Kolb | 2021-04-25 | 1 | -4/+4 |
| | |||||
* | Merge #8627 | bors[bot] | 2021-04-22 | 1 | -0/+1 |
|\ | | | | | | | | | | | | | | | 8627: Add profiling spans under cargo_to_crate_graph r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]> | ||||
| * | Add profiling spans under cargo_to_crate_graph | Laurențiu Nicola | 2021-04-22 | 1 | -0/+1 |
| | | |||||
* | | Merge #8570 | bors[bot] | 2021-04-21 | 1 | -0/+1 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | 8570: Flycheck tries to parse both Cargo and Rustc messages. r=rickvanprim a=rickvanprim This change allows non-Cargo build systems to be used for Flycheck provided they call `rustc` with `--error-format=json` and emit those JSON messages to `stdout`. Co-authored-by: James Leitch <[email protected]> | ||||
| * | | Flycheck tries to parse both Cargo and Rustc messages. | James Leitch | 2021-04-19 | 1 | -0/+1 |
| | | | |||||
* | | | Bump other deps | Laurențiu Nicola | 2021-04-21 | 1 | -6/+6 |
| | | | |||||
* | | | Bump chalk | Laurențiu Nicola | 2021-04-21 | 1 | -8/+8 |
| | | | |||||
* | | | Bump rustc_lexer | Laurențiu Nicola | 2021-04-21 | 1 | -2/+2 |
| |/ |/| | |||||
* | | fix: no longer get stuck on windows | Aleksey Kladov | 2021-04-20 | 1 | -0/+3 |
|/ | | | | | | | reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages | ||||
* | notify 5.0.0.pre7 | kjeremy | 2021-04-15 | 1 | -2/+2 |
| | | | | Fixes windows leak: https://github.com/notify-rs/notify/pull/298 | ||||
* | crossbeam-channel 0.5.1 | kjeremy | 2021-04-13 | 1 | -2/+2 |
| | | | | Fixes a potential memory leak in unbound channels. | ||||
* | Bump lsp-types and syn | kjeremy | 2021-04-08 | 1 | -4/+4 |
| | | | | This lsp-types now supports a default InsertTextMode for completion and a per-completion item commit_characters | ||||
* | Update crates | kjeremy | 2021-04-07 | 1 | -10/+10 |
| | |||||
* | Avoid duplicating VfsPath in vfs::path_interner::PathInterner by using an ↵ | Alexandru Macovei | 2021-04-06 | 1 | -0/+1 |
| | | | | IndexSet | ||||
* | Use arrayvec 0.7 to avoid perf regression in 0.6.1 | kjeremy | 2021-04-05 | 1 | -2/+2 |
| | | | | See: https://github.com/bluss/arrayvec/issues/182 | ||||
* | Check if bitflags deps pulls its weight | Aleksey Kladov | 2021-04-04 | 1 | -1/+0 |
| | | | | | | | | Bitflags is generally a good dependency -- it's lightweight, well maintained and embraced by the ecosystem. I wonder, however, do we really need it? Doesn't feel like it adds much to be honest. | ||||
* | Use bitflags to compress function properties | Jonas Schievink | 2021-04-03 | 1 | -0/+1 |
| | | | | Very minor savings, only 1 MB or so | ||||
* | cargo update | Jeremy Kolb | 2021-04-03 | 1 | -14/+14 |
| | |||||
* | Global TypeRef/TraitRef interning | Jonas Schievink | 2021-04-01 | 1 | -0/+1 |
| | |||||
* | Use arrayvec 0.6 | Laurențiu Nicola | 2021-03-25 | 1 | -2/+4 |
| | |||||
* | cargo update | kjeremy | 2021-03-23 | 1 | -40/+28 |
| | | | | Removes dependency on socket2 | ||||
* | :arrow_up: rowan | Aleksey Kladov | 2021-03-22 | 1 | -2/+2 |
| | |||||
* | Parse extended_key_value_attributes | Lukas Wirth | 2021-03-19 | 1 | -2/+2 |
| | |||||
* | Upgrade rowan | Aleksey Kladov | 2021-03-16 | 1 | -4/+2 |
| | | | | Notably, new rowan comes with support for mutable syntax trees. | ||||
* | Fix macro expansion for statements w/o semicolon | Edwin Cheng | 2021-03-16 | 1 | -2/+2 |
| | |||||
* | Return multiple modules in `parent_module` | Lukas Wirth | 2021-03-15 | 1 | -0/+1 |
| | |||||
* | Use expect-test for builtin macro/derive tests | Jonas Schievink | 2021-03-10 | 1 | -0/+1 |
| | |||||
* | Merge #7965 | bors[bot] | 2021-03-10 | 1 | -8/+8 |
|\ | | | | | | | | | | | | | | | 7965: cargo update and lexer r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]> | ||||
| * | cargo update and lexer | kjeremy | 2021-03-10 | 1 | -8/+8 |
| | | |||||
* | | Implement builtin `cfg!` macro | Jonas Schievink | 2021-03-10 | 1 | -0/+1 |
|/ | |||||
* | Merge #6822 | bors[bot] | 2021-03-09 | 1 | -0/+19 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6822: Read version of rustc that compiled proc macro r=edwin0cheng a=jsomedon Signed-off-by: Jay Somedon <[email protected]> This PR is to fix #6174. I basically * added two methods, `read_version` and `read_section`(used by `read_version`) * two new crates `snap` and `object` to be used by those two methods I just noticed that some part of code were auto-reformatted by rust-analyzer on file save. Does it matter? Co-authored-by: Jay Somedon <[email protected]> Co-authored-by: Edwin Cheng <[email protected]> | ||||
| * | Fix multiple issues from code review | Jay Somedon | 2021-03-04 | 1 | -19/+14 |
| | | | | | | | | | | | | | | | | * check metadata version * use memmap * use Result instead of unwrap with Jay Somedon <[email protected]> | ||||
| * | Read version of rustc that compiled proc macro | Jay Somedon | 2021-03-04 | 1 | -2/+26 |
| | | | | | | | | With Jay Somedon <[email protected]> | ||||
* | | Use upstream cov-mark | Laurențiu Nicola | 2021-03-08 | 1 | -0/+15 |
| | | |||||
* | | Don't punish every crate with serde-json | Aleksey Kladov | 2021-03-08 | 1 | -1/+0 |
| | | |||||
* | | Cargo update | kjeremy | 2021-03-08 | 1 | -30/+21 |
| | | | | | | | | Chalk changes just a version # bump. There are no actual commits. |