aboutsummaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
* internal: don't pull tracing via chalkAleksey Kladov2021-06-141-50/+0
|
* internal: cut deps between assists and diagnosticsAleksey Kladov2021-06-141-1/+0
|
* internal: move diagnostics to a new crateAleksey Kladov2021-06-141-0/+17
|
* internal: start ide diagnostics crateAleksey Kladov2021-06-141-0/+4
|
* internal: cross-crate cov-marksAleksey Kladov2021-06-121-2/+2
|
* minor: optimizeAleksey Kladov2021-06-121-0/+1
| | | | | We shouldn't be looking at the source map unless we actually have diagnostics.
* Merge #9204bors[bot]2021-06-111-2/+2
|\ | | | | | | | | | | | | | | | | | | 9204: feat: more accurate memory usage info on glibc Linux r=jonas-schievink a=jonas-schievink This adds support for the new `mallinfo2` API added in glibc 2.33. It addresses a shortcoming in the `mallinfo` API where it was unable to handle memory usage of more than 2 GB, which we sometimes exceed. Blocked on https://github.com/rust-lang/libc/pull/2228 Co-authored-by: Jonas Schievink <[email protected]>
| * Update libcJonas Schievink2021-06-111-2/+2
| |
* | Update ungrammarJonas Schievink2021-06-111-2/+2
| |
* | Merge #9192bors[bot]2021-06-111-0/+9
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 9192: internal: Build test-macros in a build script r=jonas-schievink a=jonas-schievink This build the test-proc-macros in `proc_macro_test` in a build script, and copies the artifact to `OUT_DIR`. This should make it available throughout all of rust-analyzer at no cost other than depending on `proc_macro_test`, fixing https://github.com/rust-analyzer/rust-analyzer/issues/9067. This hopefully will let us later write inline tests that utilize proc macros, which makes my life fixing proc macro bugs easier. Opening this as a sort of RFC, because I'm not totally sure this approach is the best. Co-authored-by: Jonas Schievink <[email protected]>
| * Build test-macros in a build scriptJonas Schievink2021-06-091-0/+9
| |
* | Make `MemoryUsage` work on WindowsJonas Schievink2021-06-101-0/+1
|/
* Simplify proc_macro_srv testsJonas Schievink2021-05-311-1/+1
|
* Merge #8866bors[bot]2021-05-311-4/+4
|\ | | | | | | | | | | | | | | 8866: Update salsa r=matklad a=jonas-schievink This updates salsa to include https://github.com/salsa-rs/salsa/pull/265, and removes all cancellation-related code from rust-analyzer Co-authored-by: Jonas Schievink <[email protected]>
| * Update to prereleaseJonas Schievink2021-05-291-2/+6
| |
| * Update salsaJonas Schievink2021-05-271-4/+0
| |
* | Merge #9062bors[bot]2021-05-301-44/+32
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 9062: internal: Bump deps r=lnicola a=lnicola Fixes #9061 bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Bump depsLaurențiu Nicola2021-05-301-44/+32
| |/
* / Attribute completion is context awareLukas Wirth2021-05-271-0/+1
|/
* Bump rustc_lexerLaurențiu Nicola2021-05-241-2/+2
|
* Bump objectLaurențiu Nicola2021-05-241-9/+3
|
* Bump misc depsLaurențiu Nicola2021-05-241-39/+45
|
* Bump chalkLaurențiu Nicola2021-05-241-8/+8
|
* Update notify and fstkjeremy2021-05-171-7/+6
|
* internal: remove one more immutable treeAleksey Kladov2021-05-141-2/+2
|
* Allow viewing the crate graph in a webviewJonas Schievink2021-05-111-0/+7
|
* internal: expose cfg attrs from hir::CrateAleksey Kladov2021-05-071-0/+1
|
* Switch from jemalloc to tikv-jemallocJohn Renner2021-05-071-34/+34
|
* Update to rowan 0.13.0-pre.5Dawer2021-05-061-2/+2
|
* Update salsaJonas Schievink2021-05-051-2/+2
|
* Replace `memmap` to `memmap2` in `proc_macro_api`memoryruins2021-05-041-11/+1
|
* cargo updateJeremy Kolb2021-05-021-36/+37
|
* Return ServerNotInitialized according to the specJeremy Kolb2021-04-271-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 depsJeremy Kolb2021-04-251-4/+4
|
* Merge #8627bors[bot]2021-04-221-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_graphLaurențiu Nicola2021-04-221-0/+1
| |
* | Merge #8570bors[bot]2021-04-211-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 Leitch2021-04-191-0/+1
| | |
* | | Bump other depsLaurențiu Nicola2021-04-211-6/+6
| | |
* | | Bump chalkLaurențiu Nicola2021-04-211-8/+8
| | |
* | | Bump rustc_lexerLaurențiu Nicola2021-04-211-2/+2
| |/ |/|
* | fix: no longer get stuck on windowsAleksey Kladov2021-04-201-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.pre7kjeremy2021-04-151-2/+2
| | | | Fixes windows leak: https://github.com/notify-rs/notify/pull/298
* crossbeam-channel 0.5.1kjeremy2021-04-131-2/+2
| | | | Fixes a potential memory leak in unbound channels.
* Bump lsp-types and synkjeremy2021-04-081-4/+4
| | | | This lsp-types now supports a default InsertTextMode for completion and a per-completion item commit_characters
* Update crateskjeremy2021-04-071-10/+10
|
* Avoid duplicating VfsPath in vfs::path_interner::PathInterner by using an ↵Alexandru Macovei2021-04-061-0/+1
| | | | IndexSet
* Use arrayvec 0.7 to avoid perf regression in 0.6.1kjeremy2021-04-051-2/+2
| | | | See: https://github.com/bluss/arrayvec/issues/182
* Check if bitflags deps pulls its weightAleksey Kladov2021-04-041-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 propertiesJonas Schievink2021-04-031-0/+1
| | | | Very minor savings, only 1 MB or so
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 01:08:15 +0000