rustfmt can't understand configured module path attributes

[fitzgen]

I have a module that has different implementations depending on what the target is. I use #[cfg_attr(..., path = "...")] to choose the correct implementation.

https://github.com/fitzgen/wee_alloc/blob/master/wee_alloc/src/lib.rs#L237-L246

#[cfg(all(not(unix), not(target_arch = "wasm32")))]
compile_error! {
    "There is no `wee_alloc` implementation for this target; want to send a pull request? :)"
}

#[cfg_attr(target_arch = "wasm32",
           path = "./imp_wasm32.rs")]
#[cfg_attr(all(unix, not(target_arch = "wasm32")),
           path = "./imp_unix.rs")]
mod imp;

rustfmt seems unable to handle this:

$ cargo fmt --all
error[E0583]: file not found for module `imp`
   --> /home/fitzgen/wee_alloc/wee_alloc/src/lib.rs:246:5
    |
246 | mod imp;
    |     ^^^
    |
    = help: name the file either imp.rs or imp/mod.rs inside the directory "/home/fitzgen/wee_alloc/wee_alloc/src"

I would expect that it would use the host target by default, or otherwise maybe hit the compile_error or something.

$ cargo fmt --version
0.3.6-nightly (e0e3e22 2018-01-18)

Full Steps to Reproduce

• clone and checkout https://github.com/fitzgen/wee_alloc/blob/b162ed4f33d127d8b00bc38281116e51f50dd2bd
• $ cd wee_alloc/
• $ cargo fmt --all

[fitzgen]

For anyone else who hits this issue, as a workaround, if I change my code to

#[cfg(all(not(unix), not(target_arch = "wasm32")))]
compile_error! {
    "There is no `wee_alloc` implementation for this target; want to send a pull request? :)"
}

#[cfg(target_arch = "wasm32")]
mod imp_wasm32;
#[cfg(target_arch = "wasm32")]
use imp_wasm32 as imp;

#[cfg(all(unix, not(target_arch = "wasm32")))]
mod imp_unix;
#[cfg(all(unix, not(target_arch = "wasm32")))]
use imp_unix as imp;

then cargo fmt --all works.

[topecongiro]

cc #1208.

[topecongiro]

I think we need to mimic some setups of rustc (ones in librustc_driver). I am not sure how, though.

[phansch]

fwiw, clippy is also having issues with cfg_attr: rust-lang/rust-clippy#1522

I guess it's the same cause? Unfortunately I don't know enough about the compiler internals yet, to be sure.

[mjbshaw]

Edit: On reflection, I filed a separate issue for this (#3427) as it seems related but separate.

This is now an issue with Rust 2018's path clarity, where submodules no longer require mod.rs. Example:

$ mkdir foo
$ touch foo/bar.rs
$ echo 'mod bar;' > foo.rs
$ rustfmt --edition 2018 foo.rs
error[E0583]: file not found for module `bar`
 --> /private/tmp/demo/foo.rs:1:5
  |
1 | mod bar;
  |     ^^^
  |
  = help: name the file either bar.rs or bar/mod.rs inside the directory "/private/tmp/demo"

For clarity, the file structure is:

$ tree
.
├── foo
│   └── bar.rs
└── foo.rs

Here, foo.rs is the Rust 2018 equivalent of Rust 2015's foo/mod.rs.

[crlf0710]

Just meet this on my code, my code is:

#[cfg_attr(feature = "winit", path = "ui_winit.rs")]
#[cfg_attr(not(feature = "winit"), path = "ui_apiw.rs")]
mod ui;

[carllerche]

I have hit this issue as well here.