default methods are broken cross crate when defined on structs

[thestinger]

let xs = [1, 2, 3, 9, 11]; xs.iter().take_(2).size_hint()

<anon>:9:36: 10:5 error: internal compiler error: method not found in AST map?!
<anon>:9          let xs = [1, 2, 3, 9, 11]; xs.iter().take_(2).size_hint()
<anon>:10     };

[pnkfelix]

Part of #2794

[Aatch]

A quick check shows it happens during privacy checking and the error is emitted on line 127 of privacy.rs.

[thestinger]

@Aatch: that's probably just the first thing to look for it

[Aatch]

@thestinger looks like you're right. I did a little more digging and it looks like default methods are pulled out of the crate metadata in this instance. Inlining is strange because the definition is considered to be in the local crate, but also not, depending on who you ask...

[msullivan]

It isn't clear to me that inline is actually related to this... I see what is going wrong and my biggest question at this point is how anything /ever/ works... Continuing to investigate.

[msullivan]

Got it. If the type of the receiver is a struct, privacy checking breaks when you try to invoke a default method from another crate. Renamed the bug.

[msullivan]

Have a fix that I'll push soon.