triage: I-nominated
This is a bug if the importing module should be able to see the private items. E.g., ``` struct Foo; mod sub { import super::*; type Bar = Foo; // Error: use of undeclared type name Foo } ``` I think there is a backwards compatibility hazard here, because if there is already an item called `Foo` in `sub` then we currently get no error, but we ought to get a name clash (unless we allow shadowing in this case). triage: I-nominated
triage: I-nominated (1.0 beta) back-compat issue
triage: P-low ()
@alexcrichton In case it matters for bookkeeping: GitHub is still labeling this issue P-low, despite your triage: P-high comment.
triage: P-high not 1.0 blocker. (Tempted to make it P-low, but I think all ICE's should probably get at least P-high).
triage: P-backcompat-lang (1.0 beta) -- soundness violation
triage: P-backcompat-lang (1.0 beta) -- at least for the backwards incompatible parts of rust-lang/rfcs#495. This is something of a nice to have, we can live with it if it doesn't get done.
testing, ignore this triage: I-nominated (1.0 beta)
triage: I-nominated
triage: I-nominated (1.0 beta)
triage: P-high
triage P-high
triage P-high
triage P-high
triage: I-nominated
triage P-high
triage: P-high I think the `panic!(anything)` aspect of `panic!` will make quite hard to overcome a limitation such as this, and I also think that we should audit whether that's actually an interface we want to support at this time. [match: triage: P-high,P-high,]
triage: I-nominated [match: triage: I-nominated,I-nominated,]