matthewjasper

This seems to be a general issue with how chalk handles elaborating environment clauses. The second test case here shows this best, there are two different FromEnv traits that are...

#638 handles opaque types

Sorry about taking so long on this r? @matthewjasper @bors r+

@bors r+

I meant something like this: ```rust pub mod a { pub use crate::b::*; pub struct A {} } mod b { pub use crate::a::*; pub use crate::c::*; pub struct B...

The tests still only have `#[cfg(target_endian = "little")]` blocks.

The macro doesn't appear to be needed here, the following also compiles. ```rust mod foo { fn bar() {} } fn main() { bar(); } ```

I think that the cfg visitor is not even processing these items.

I think this may have meant the list in items.md but that list doesn't look correct for this statement (as extern crates are on that list). I think this page...