Closed Wilfred closed 7 years ago
When I try the above settings on a test crate, I can indeed reproduce the issue. Thanks for the report 👍
cargo build
reports no error. And removing the --test
flag to cargo rustc
makes the error go away. I don't really understand why rustc reports an error here, but I haven't looked into custom panic handles in Rust.
Regardless, we should be able to report the error as-is in Flycheck. It seems the suspicious state stems from not collecting errors that have empty spans (no filename info).
I've sent a PR which should fix this issue.
Fixed in flycheck/flycheck#1182.
I have a rust project that contains the following in its Cargo.toml:
The command that gets run is:
This can't be parsed by flycheck: