You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#[crate_type = "lib"];
mod test { pub type I = int; }
b.rs:
#[crate_type = "lib"];
extern mod a;
use a::test::*;
fn foo(i: I) {}
I'm compiling it with rustc:
rustc a.rs
rustc -L . b.rs
It used to work, but it now gives the error message:
b.rs:6:10: 6:11 error: use of undeclared type name `I`
However, the problem here is not with I - the problem is with module (adding pub to test module fixes the error). Is it possible to emit an error at 'use a::test::*' instead?
The text was updated successfully, but these errors were encountered:
Closing this in favor of #8215. In moving privacy out of resolve, this should yield a much better error message of type "I" is private instead of a cryptic undeclared type name.
use `is_integer_literal` more
I noticed that we have the `is_integer_literal` function in our `clippy_utils`, yet almost everywhere people still match int literal expressions manually. So I searched for instances to replace and shorten the code a bit.
---
changelog: none
I have two modules, a.rs and b.rs.
a.rs:
b.rs:
I'm compiling it with rustc:
It used to work, but it now gives the error message:
However, the problem here is not with I - the problem is with module (adding
pub
to test module fixes the error). Is it possible to emit an error at 'use a::test::*' instead?The text was updated successfully, but these errors were encountered: