non-public mod_path?

[dwrensha]

It looks like mod_path always inserts the pub keyword.

Would it make sense to change this, so that

mod_path! foo (concat!(env!("OUT_DIR"), "/hello.rs"))

would instead expand to

#[path = "path/to/OUT_DIR/hello.rs"]
mod foo;

and maybe

pub_mod_path! foo (concat!(env!("OUT_DIR"), "/hello.rs"))

would expand to

#[path = "path/to/OUT_DIR/hello.rs"]
pub mod foo;

?

[SimonSapin]

I’d take a PR to do this.

Note though that the use case for mod_path became much weaker when rust-lang/rust#20179 landed. I prefer using something like this:

#[macro_use]
mod foo {
    include!(concat!(env!("OUT_DIR"), "/foo.rs"));
}

#[macro_use] had to be moved there from #![macro_use] in the included file because of rust-lang/rfcs#752