rust-analyzer: Why rust-analyzer doesn't work in [test] function?
#[test]
fn test_fn(){
... //rust-analyzer doesn't work here! NO error prompt until you really compile file.
}
Is it a bug or a config/setting which should properly toggled?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (7 by maintainers)
@Wyvern I confirm that
--all-targetsneed to be enabled. It should probably be enabled by default, there’s no reason to avoid showing errors on test. For reference, my setup on vscode isHad the same issue. The solution is to enable experimental diagnostics mode. My neovim specific lsp config:
and for VS Code users, I think this should suffice:
I was able to resolve this similar to @nikkolasg but I had to enable checking tests, examples, and benches explicitly as well:
Thank you - this was bothering me so much. I’m not sure why some projects need this and others do not.