I'm trying to work on a project that the RLS extension has no problem handling but I'm getting an odd error from rust-analyzer that is pretty unhelpful:

rust-analyzer failed to load workspace: cargo metadata failed: No such file or directory (os error 2)

What file or directory could not be found? Why couldn't it be found even though RLS works without a hitch?

I'm running the VSCode extension remotely (Docker) with VSCode Insiders and rust-analyzer at commit 759100fb0dcb41518f2a593dae5de5bbedd07776.

I installed rust with brew on MacOS, and I'm noticing this error on a hello world project with VS Code:

rust-analyzer failed to load workspace: 
    Failed to find sysroot for Cargo.toml file ./rust_new/Cargo.toml. 
    Is rust-src installed?: rustup component add rust-src failed

I didn't install with rustup, and I figured I wouldn't need to. This suggests I must, but why? Does this suggest I need the complier source to use your package in my editor?

Both ra_hir and ra_ide_api are really slow to compiler, which makes fix & test loop rather frustrating. Note that tests are extremely fast themselves, it's compile time that hurts us badly.

We need to do something with it...

Fixes: Issue#1294

TODO:

• [x] Load themes
• [x] Load existing ralsp-prefixed overrides from "workbench.colorCustomizations".
• [x] Load overrides from "editor.tokenColorCustomizations.textMateRules".
• [x] Use RA tags to load vscode.DecorationRenderOptions (colors) from theme & overrides.
• [x] Map RA tags to common TextMate scopes before loading colors.
• [x] Add default scope mappings in extension.
• [x] Cache mappings between settings updates.
• [x] Add scope mapping configuration manifest in package.json
• [x] Load configurable scope mappings from settings.
• [x] Load JSON Scheme for text mate scope rules in settings.
• [x] Update Readme.

Borrowed the theme loading (scopes.ts) from Tree Sitter with some modifications to reading "editor.tokenColorCustomizations" for merging with loaded themes and had to remove the async portions to be able to load it from settings updates.

~Just a PoC and an idea I toyed around with a lot of room for improvement.~ For starters, certain keywords aren't part of the standard TextMate grammar, so it still reads colors from the ralsp prefixed values in "workbench.colorCustomizations".

But I think there's more value making the extension work with existing themes by maping some of the decoration tags to existing key or keys.

These will merge with the default ones coming with the extension, so you don't have to implement all of them and works well with overrides defined in settings.

    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": "keyword",
                "settings": {
                    "fontStyle": "bold",
                }
            },
        ]
    },

Edit: The idea is to work with 90% of the themes out there by working within existing scopes available that are generally styled. It's not to say I want to erase the custom Rust scopes - those should still remain and eventually worked into a custom grammar bundle for Rust specific themes that target those, I just want to make it work with generic themes offered on the market place for now.

A custom grammar bundle and themes for Rust specific scopes is out of... scope for this PR. We'll make another round to tackle those issues.

Current fallbacks implemented

    [
        'comment',
        [
            'comment',
            'comment.block',
            'comment.line',
            'comment.block.documentation'
        ]
    ],
    ['string', ['string']],
    ['keyword', ['keyword']],
    ['keyword.control', ['keyword.control', 'keyword', 'keyword.other']],
    [
        'keyword.unsafe',
        ['storage.modifier', 'keyword.other', 'keyword.control', 'keyword']
    ],
    ['function', ['entity.name.function']],
    ['parameter', ['variable.parameter']],
    ['constant', ['constant', 'variable']],
    ['type', ['entity.name.type']],
    ['builtin', ['variable.language', 'support.type', 'support.type']],
    ['text', ['string', 'string.quoted', 'string.regexp']],
    ['attribute', ['keyword']],
    ['literal', ['string', 'string.quoted', 'string.regexp']],
    ['macro', ['support.other']],
    ['variable', ['variable']],
    ['variable.mut', ['variable', 'storage.modifier']],
    [
        'field',
        [
            'variable.object.property',
            'meta.field.declaration',
            'meta.definition.property',
            'variable.other'
        ]
    ],
    ['module', ['entity.name.section', 'entity.other']]

EDIT: see https://github.com/rust-analyzer/rust-analyzer/issues/11080#issuecomment-1010840901

rust-analyzer version: "Rust Analyzer: Show RA Version" command does nor exist, extension install dir: matklad.rust-analyzer-0.2.867

rustc version: rustc 1.56.0 (09c42c458 2021-10-18)

OS Version: Ubuntu 18.04.6

VS Code version: I use VSCodium 1.63.2

Today, rust-analyzer updated itself and stop working with the error:

INFO [12/21/2021, 11:18:12 AM]: Using server binary at /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer
ERROR [12/21/2021, 11:18:12 AM]: Bootstrap error [Error: Failed to execute /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer --version
	at j0 (/home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/out/main.js:109:4032)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async N0 (/home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/out/main.js:109:1881)
	at async I0 (/home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/out/main.js:108:3977)
	at async lC (/home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/out/main.js:108:3808)
	at async Promise.all (index 0)
	at async v.$activate (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:100:20806)]

The file /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer but cannot be executed, even manually:

$ /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer --version
bash: /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer: No such file or directory

While the file exists.

But ldd on it shows the missing musl lib:

ldd /home/user/.vscode-oss/extensions/matklad.rust-analyzer-0.2.867/server/rust-analyzer
        linux-vdso.so.1 (0x00007ffce3bfa000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f5dc6a52000)
        libc.musl-x86_64.so.1 => not found
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5dc6661000)
        /lib/ld-musl-x86_64.so.1 => /lib64/ld-linux-x86-64.so.2 (0x00007f5dc8490000)

I had a VSCodium update yesterday so it might be related.

I have tried to uninstall the extension but it installs the same version.

Struct EditTree will more directly mutate the syntax tree by building up nodes with knowledge of Pattern's, checking as we walk the tokens and inserting edits marked with location and other meta info. When a diff is asked for the tree will know the amount, size and type of edit capable of producing a diff. relevant files: edit_tree the new way to directly mutate tree scratch just to get something to output to see what I'm doing otherwise everything so far is similar or stolen from nixpkgs-fmt :smile:

Would it make sense for rowan node's to be able to insert tokens, or is keeping a vec of edits to create a diff which some other thing can interpret and build the appropriate string out of more the direction to go in.

I tried to search if it was reported but didn't found anything.

When importing the platform specific modules in std::os rust-analyzer gives me the following error: unresolved import. Also those modules don't show up for auto-complete.

When the module is used outside use statement, there is no error, but the semantic token are of the type unresolvedReference.

RA version

Latest master branch

Example

use std::os::unix;

rust-analyzer version: rust-analyzer 2022-02-14 (installed via pacman)

rustc version: rustc 1.58.1 (db9d1b20b 2022-01-20) (installed via rustup and branch is stable)

Hello! I am taking this error on vscode.

rust-analyzer failed to load workspace: "cargo" "--version" failed, exit status: 1
stderr:
error: no override and no default toolchain set

I am using pre-release of vscode extension, that's why i open a issue despite your info about it. I tried adding CARGO path but it didn't work. I hope it'll be helpful bug report for you!

rustup can now install rust-analyzer for the stable tool-chain. This commit removes the note that rustup can only install for the nightly branch and adjusts the command.

I also added a note on how to find the path to the rust-analyzer binary when installed using rustup, and suggestions on how to work around it not being placed in ~/.cargo/bin.

I thought it would be ideal to point everyone to use rustup run stable rust-analyzer to start rust-analyzer. That would make it trivial to switch to nightly however I could not get this to work in nvim therefore I left it as a suggestion at the end.

rust-analyzer version: v0.3.1091

rustc version: rustc 1.61.0 (fe5b13d68 2022-05-18)

When using IntEnum proc macro rust analyzer gives the error:

proc macro IntEnum not expanded rust-analyzer unresolved-proc-macro

rust-analyzer no longer will run on Ubuntu 18.04( which bundles glibc 2.27), and other distros which have a glibc older than 2.27.

this issue manifests as a "Bootstrap Error" notably, the extension output will log something along the lines of:

ERROR [2/28/2022, 8:46:56 AM]: Bootstrap error [Error: Failed to execute /home/newuser/.vscode/extensions/matklad.rust-analyzer-0.2.956/server/rust-analyzer --version

when running the binary, we get the following error:

/home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer)
/home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/jake/.vscode-server-insiders/extensions/matklad.rust-analyzer-0.3.953/server/rust-analyzer)

current workarounds are mentioned in this comment: https://github.com/rust-analyzer/rust-analyzer/issues/11558#issuecomment-1054802255

Closes #13872 CC #7747 CC #10371

This allows us to ship a format that's easier to handle on Windows. As a bonus, we can also include the PDB, to get useful stack traces. Unfortunately, it adds a couple of dependencies to xtask, increasing the debug build times from 1.28 to 1.58 s (release from 1.60s to 2.20s) on my system.

rust-analyzer version: rust-analyzer 1.67.0-nightly (83356b7 2022-11-17)

rustc version: rustc 1.67.0-nightly (83356b78c 2022-11-17)

relevant settings: nothing out of the ordinary, I think, but I'm using this in Helix

Expected behavior: using the Extract into Function action extracts the highlighted code into a function exactly without changing whitespace/newlines.

Behavior: it removes newlines.

fn some_long_function() {
  let foo = bar();
  let bax = quux();

  // If I highlight from here ... {
  let foo2 = foo * 2;

  let frob = baz.frobnicate();
  frob.process();
  // } to here, and extract into function,
  // the newline after `let foo2 = foo*2` is removed.
}

I think it does make sense to auto-format the code because it'll format on save anyways (hopefully), but it is kind of weird for the newlines to disappear because then I have to go back and insert all the newlines again ... I'd imagine that's tricky to implement though (I don't know about rust-analyzer's internals but I'd imagine this action operates on the AST more than text).

For example, if you start with the following code:

use std::io::Result;
fn main() {
    let f1 = std::fs::File::create("/tmp/test.txt");
}

Select Insert explicit type on f1. It inserts the type Result<std::fs::File, std::io::Error>, which fails to compile because the Result that is in scope only takes a single type parameter, not two.

error[E0107]: this type alias takes 1 generic argument but 2 generic arguments were supplied
  --> src/main.rs:3:13
   |
3  |     let f1: Result<std::fs::File, std::io::Error> = std::fs::File::create("/tmp/test.txt");
   |             ^^^^^^                -------------- help: remove this generic argument
   |             |
   |             expected 1 generic argument
   |

The same issue can be observed with Extract into function and also with other types from the prelude, e.g. String, Vec etc - although those are less likely to be an issue because the standard library doesn't supply alternative items with those names like it does for Result.

Expected behaviour would be that Result would be fully qualified as std::result::Result, since the prelude import isn't available.

Observed with rust-analyzer built from head (f31733b1d 2022-12-31).

Use .zip for rust-analyzer-x86_64-pc-windows-msvc instead of .gz using gz will require downloading some softwares like WinZip but I prefer not to and just use windows' explorer.

rust-analyzer version: rust-analyzer version: 0.3.1334-standalone (74ae2dd30 2022-12-25)

rustc version: rustc 1.66.0 (69f9c33d7 2022-12-12)

relevant settings: in vscode's settings.json: "rust-analyzer.diagnostics.experimental.enable": true, "rust-analyzer.checkOnSave.enable": false (to opt-in into type checking diagnostics)

This code:

struct Foo<T: ?Sized> {
    leading: u32,
    trailing: T,
}

fn unsize(x: Box<Foo<[u32; 4]>>) -> Box<Foo<[u32]>> {
    x
}

compiles fine with rustc, but vscode shows type error from rust-analyzer: