#![no_std] can't find crate for test

[imjasonmiller]

I'm posting this for posterity's sake, as someone else might run into the issue and find it useful.

I kept receiving the following error:

It seems it's related to the following issues:

• no_std Can't find crate for 'test' vscode-rust#729
• no_std targets, can't find crate for test rls#1524

As coc.nvim offers per project based settings, I added the following configuration and relevant target to my project, which will make the error go away:

.vim/coc-settings.json

{
  "rust.target": "thumbv7em-none-eabihf",
  "rust.all_targets": false
}

System information

nvim v0.5.0-392-gff1730373
coc-rust-analyzer 0.4.3
rustc 1.41.0 (5e1a79984 2020-01-27)
rust-analyzer cba3c99

[stenpeeters]

I observed the same issue in Eclipse while using the Corrosion plugin with rust-analyzer. For embedded code, with the #![no-std] attribute, Eclipse would always show the "can't find crate for 'test'" error.

I solved the problem by creating a json file with the following content:
./rls.json

{
"checkOnSave": {
"allTargets": false
}
}

Then in Eclipse, go to Window-> Preferences --> Rust

and add the file path to the "LS configuration" field. This assumes that the Language server is properly configured.

[pooladkhay]

Fix for VSCode:
{PROJECT_DIR}/.vscode/settings.json:

{
   "rust-analyzer.checkOnSave.allTargets": false,
}

[tomasApo]

@pooladkhay this also fixed my issue. I had a #![no_std] test crate issue for months on VSCODE. Thank you

[mlavacca]

With the rust-analyzer VSCode plugin's latest version (v0.3), the fix is:

{
   "rust-analyzer.check.allTargets": false,
}