Configuring rust-analyzer for an embedded rust project (no_std)

[esden]

Hi,

To be able to use Zed for rust on embedded systems it is necessary to turn off the allTargets option, otherwise all files with the no_std setting will be plastered with the rustc: can't find crate for 'test' error.

I tried to follow the documentation but the setting does not seem to do anything. The zed logfile is not verbose enough to indicate what options are used for the execution of check either.

My workspace config is as follows:

{
  "lsp": {
    "rust-analyzer": {
      "initialization_options": {
        "check": {
          "allTargets": false,
          "targets": "thumbv8m.main-none-eabihf"
        }
      }
    }
  }
}

The above does not seem to have any impact on the lsp errors.

In contrast the following config does work in vscode:

{
  "rust-analyzer.cargo.target": "thumbv8m.main-none-eabihf",
  "rust-analyzer.check.allTargets": false,
  "rust-analyzer.check.extraArgs": [
    "--target",
    "thumbv8m.main-none-eabihf",
    "--bins"
  ]
}

I am running Zed 0.177.9 on ARM Mac OS.

Any help would be appreciated, I would love to give Zed a chance to replace VSCode but this is a bit of a showstopper for me.

Cheers,
Piotr

[esden]

I have tested things on Linux, and the same configuration appears to be working fine while it fails on a Mac. So after all it might be some bug that is causing problems here.

[esden]

Now that I have done extra testing I am pretty sure it is a bug in zed. I have opened an issue #27637 to document this problem.

As it is now an issue I think this discussion can be closed.