Using log or getops crates reports "multple matching crates" error to be displayed

[hugoduncan]

For some crates (at least log and getopts), declaring extern crate getopts; leads to the following errors displayed in flycheck:

Multiple matching crates for `getopts`
can't find crate for `getopts`

This seems to be caused by the existence of log and getopts library files in rustlib.

Cargo doesn't report the same errors when run directly, as it uses different rustc arguments to flycheck-rust (-L dependency=… and --extern …=…).

[mcobzarenco]

+1

[swsnr]

@hugoduncan Feel free to open a pull request to improve flycheck-rust. I don't have the time to fix this issue currently, and I don't use Rust anymore.

[hugoduncan]

Unfortunately it doesn't seem like a trivial fix, and will probably involve updating the rust support in flycheck itself. I can't see a way of doing it corrctly without parsing the Cargo.toml file.

[hugoduncan]

It seemed simplest just to invoke cargo. I started flycheck-cargo.

[swsnr]

@hugoduncan Cargo would build the entire project to check a single file, wouldn't it?

[hugoduncan]

@lunaryorn Yes, and it definitely has speed issues.

[utkarshkukreti]

Would this help: rust-lang/cargo#1225?

[swsnr]

@utkarshkukreti Probably, though a structured format would be better, i.e. JSON.

[swsnr]

Effectively blocked by rust-lang/cargo#1434.

[swsnr]

Closing, in favour of #8