aboutsummaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* Update crateskjeremy2020-05-261-10/+10
|
* Fix Cargo.lockAleksey Kladov2020-05-241-14/+17
|
* Merge pull request #4548 from bnjjj/fix_4464Aleksey Kladov2020-05-241-0/+3
|\ | | | | add support of feature flag for runnables
| * add support of feature flag for runnables #4464Benjamin Coenen2020-05-231-0/+3
| | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
* | Update to rustc_lexer version 660.Julian Wollersberger2020-05-241-2/+2
| | | | | | | | Change `unescape_*()` to `unescape_literal()`.
* | Update ChalkFlorian Diebold2020-05-221-28/+13
| | | | | | | | | | As always, this just makes compilation work, we don't use the newly available functionality yet.
* | LSP: Two stage initializationkjeremy2020-05-191-2/+2
|/ | | | | | | | | | Fills in server information. Derives CodeAction capabilities from the client. If code action literals are unsupported we fall back to the "simple support" which just sends back commands (this is already supported in our config). The difference being that we did not adjust our server capabilities so that if the client was checking for `CodeActionProvider: "true"` in the response that would have failed.
* Update crateskjeremy2020-05-191-22/+22
|
* Chalk upgradeFlorian Diebold2020-05-161-12/+12
|
* Better structureAleksey Kladov2020-05-151-1/+0
|
* Move LSP bits from flycheck to rust-analyzerAleksey Kladov2020-05-151-2/+2
| | | | | There should be only one place that knows about LSP, and that place is right before we spit JSON on stdout.
* Update crateskjeremy2020-05-131-6/+6
| | | | Documentation improvements
* Update crateskjeremy2020-05-121-33/+45
|
* :arrow_up: ra_vfsAleksey Kladov2020-05-101-2/+2
| | | | | Fix a critical bug where \r\n line endings would accidentally sneak in after in-memory overlay removal.
* Merge #4406 #4410 #4411 #4417bors[bot]2020-05-101-6/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4406: Update cargo-metadata r=matklad a=edwin0cheng This PR update `cargo-metadata` to 0.10.0 and it also relax the` serde-derive` deps to 1.0 for tests in `proc-macro-srv`. cc @robojumper r= @matklad , I think you would have something to say related to https://github.com/serde-rs/json/issues/647#issue-593788429 ? 4410: Improve wording in comment r=matklad a=edwin0cheng 4411: do not remove then block when you unwrap else block #4361 r=matklad a=bnjjj close #4361 4417: Omit default types in HirDisplay SourceCode mode r=matklad a=TimoFreiberg Closes #4390 Co-authored-by: Edwin Cheng <[email protected]> Co-authored-by: Benjamin Coenen <[email protected]> Co-authored-by: Timo Freiberg <[email protected]>
| * Update cargo-metadataEdwin Cheng2020-05-091-6/+6
| |
* | CleanupAleksey Kladov2020-05-081-1/+0
| |
* | Rename ra_env -> ra_toolchainAleksey Kladov2020-05-081-10/+10
|/
* Merge #4329bors[bot]2020-05-081-0/+19
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4329: Look for `cargo`, `rustc`, and `rustup` in standard installation path r=matklad a=cdisselkoen Discussed in #3118. This is approximately a 90% fix for the issue described there. This PR creates a new crate `ra_env` with a function `get_path_for_executable()`; see docs there. `get_path_for_executable()` improves and generalizes the function `cargo_binary()` which was previously duplicated in the `ra_project_model` and `ra_flycheck` crates. (Both of those crates now depend on the new `ra_env` crate.) The new function checks (e.g.) `$CARGO` and `$PATH`, but also falls back on `~/.cargo/bin` manually before erroring out. This should allow most users to not have to worry about setting the `$CARGO` or `$PATH` variables for VSCode, which can be difficult e.g. on macOS as discussed in #3118. I've attempted to replace all calls to `cargo`, `rustc`, and `rustup` in rust-analyzer with appropriate invocations of `get_path_for_executable()`; I don't think I've missed any in Rust code, but there is at least one invocation in TypeScript code which I haven't fixed. (I'm not sure whether it's affected by the same problem or not.) https://github.com/rust-analyzer/rust-analyzer/blob/a4778ddb7a00f552a8e653bbf56ae9fd69cfe1d3/editors/code/src/cargo.ts#L79 I'm sure this PR could be improved a bunch, so I'm happy to take feedback/suggestions on how to solve this problem better, or just bikeshedding variable/function/crate names etc. cc @Veetaha Fixes #3118. Co-authored-by: Craig Disselkoen <[email protected]> Co-authored-by: veetaha <[email protected]>
| * use home crate instead of dirsCraig Disselkoen2020-05-071-76/+11
| |
| * pull function out into new crate ra_env; use in ra_flycheck as wellCraig Disselkoen2020-05-061-1/+10
| |
| * ra_project_model: look for Cargo in more placesCraig Disselkoen2020-05-061-1/+76
| | | | | | | | See #3118
* | Update depskjeremy2020-05-071-16/+16
|/
* Update crateskjeremy2020-05-011-6/+6
|
* Bump depsLaurențiu Nicola2020-05-011-24/+44
|
* Add support for incremental text synchronizationLaurențiu Nicola2020-04-301-2/+2
|
* lsp-types 0.74kjeremy2020-04-261-4/+4
| | | | | * Fixes a bunch of param types to take partial progress into account. * Will allow us to support insert/replace text in completions
* Extract messy tree handling out of profiling codeAleksey Kladov2020-04-251-0/+1
|
* text-size 1.0.0Aleksey Kladov2020-04-251-2/+6
|
* Convert code to text-sizeAleksey Kladov2020-04-251-10/+6
|
* :arrow_up: crates (to bust the caches)Aleksey Kladov2020-04-241-10/+10
|
* cargo updatekjeremy2020-04-221-8/+8
|
* Improve remove dervie attrsEdwin Cheng2020-04-211-0/+1
|
* Update Chalk, and cache Chalk env elaboration through a queryFlorian Diebold2020-04-201-6/+6
| | | | This should fix some of the worst performance problems.
* Update regexJeremy Kolb2020-04-191-2/+2
|
* Use mmap for proc macro libsLaurențiu Nicola2020-04-171-0/+11
|
* Merge #3958bors[bot]2020-04-161-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3958: Add proc-macro related config and tests r=matklad a=edwin0cheng This PR do the following things: 1. Add cli argument `proc-macro` for running proc-macro server. 2. Added support for proc-macro in bench and analysis-stats 3. Added typescript config for proc-macros 4. Added an heavy test for proc-macros. To test it out: 1. run `cargo xtask install --proc-macro` 2. add `"rust-analyzer.cargo.loadOutDirsFromCheck": true"` and `"rust-analyzer.procMacro.enabled": true"` in vs code config. [Edit] Change to use `rust-analyzer proc-macro` for running proc-macro standalone process. Co-authored-by: Edwin Cheng <[email protected]>
| * Add proc-macro cli command for rust-analyzerEdwin Cheng2020-04-161-0/+1
| |
* | cargo updatekjeremy2020-04-161-10/+10
| |
* | Update ChalkFlorian Diebold2020-04-161-6/+6
|/
*-. Merge #3964 #3965 #3967bors[bot]2020-04-151-0/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3964: Nicer Chalk debug logs r=matklad a=flodiebold I'm looking at a lot of Chalk debug logs at the moment, so here's a few changes to make them slightly nicer... 3965: Implement inline associated type bounds r=matklad a=flodiebold Like `Iterator<Item: SomeTrait>`. This is an unstable feature, but it's used in the standard library e.g. in the definition of Flatten, so we can't get away with not implementing it :) (This is cherry-picked from my recursive solver branch, where it works better, but I did manage to write a test that works with the current Chalk solver as well...) 3967: Handle `Self::Type` in trait definitions when referring to own associated type r=matklad a=flodiebold It was implemented for other generic parameters for the trait, but not for `Self`. (Last one off my recursive solver branch :smile: ) Co-authored-by: Florian Diebold <[email protected]>
| * | Nicer display of projections in Chalk logsFlorian Diebold2020-04-131-0/+1
| |/
* | Merge #3963bors[bot]2020-04-151-6/+19
|\ \ | | | | | | | | | | | | | | | | | | | | | 3963: Upgrade Chalk r=matklad a=flodiebold Co-authored-by: Florian Diebold <[email protected]>
| * | Upgrade ChalkFlorian Diebold2020-04-131-6/+19
| |/
* / insta 0.16kjeremy2020-04-141-2/+2
|/
* Merge #3920bors[bot]2020-04-111-0/+49
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3920: Implement expand_task and list_macros in proc_macro_srv r=matklad a=edwin0cheng This PR finish up the remain `proc_macro_srv` implementation : 1. Added dylib loading code for proc-macro crate dylib. Note that we have to add some special flags for unix loading because of a bug in old version of glibc, see https://github.com/fedochet/rust-proc-macro-panic-inside-panic-expample/issues/1 and https://github.com/rust-lang/rust/issues/60593 for details. 2. Added tests for proc-macro expansion: We use a trick here by adding `serde_derive` to dev-dependencies and calling `cargo-metadata` for searching its dylib path, and expand it in our tests. [EDIT] Note that this PR **DO NOT** implement the final glue code with rust-analzyer and proc-macro-srv yet. Co-authored-by: Edwin Cheng <[email protected]>
| * Add testsEdwin Cheng2020-04-091-0/+1
| |
| * Add dylib loading codeEdwin Cheng2020-04-091-0/+48
| |
* | cargo updatekjeremy2020-04-101-10/+10
| |
* | Implement Chalk's debug methods using TLSFlorian Diebold2020-04-101-0/+7
|/ | | | | | | | | | Chalk now panics if we don't implement these methods and run with CHALK_DEBUG, so I thought I'd try to implement them 'properly'. Sadly, it seems impossible to do without transmuting lifetimes somewhere. The problem is that we need a `&dyn HirDatabase` to get names etc., which we can't just put into TLS. I thought I could just use `scoped-tls`, but that doesn't support references to unsized types. So I put the `&dyn` into another struct and put the reference to *that* into the TLS, but I have to transmute the lifetime to 'static for that to work.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 16:28:50 +0000