Repository navigation
bounds in ty params can't seem to refer to other ty params #2611
Description
This is more-or-less taken from commented-out code in core::iter-trait:
import iter;
import iter::base_iter;
impl Q<A> for base_iter<A> {
fn flat_map_to_vec<B:copy, IB:base_iter<B>>(op: fn(B) -> IB) -> [B] {
iter::flat_map_to_vec(self, op)
}
}
This fails to compile with unresolved typename: B. That's not right, since the method should get resolved in a scope that includes its own ty params. Strangely enough, the same function does compile if it's not inside an impl and takes its self arg explicitly.
Activity
catamorphism commentedon Jun 15, 2012
Adding (xfailed) test case as run-pass/issue-2611.rs
bstrie commentedon Jul 17, 2012
Post-0.3, the test case gives this error instead:
Not sure whether or not the message is accurate, but it's certainly unhelpful.
catamorphism commentedon Jul 17, 2012
I'll try fixing the error message.
msullivan commentedon Aug 23, 2012
Now it fails with a message saying they have incompatible type parameters. I think I'm going to look into this some.
catamorphism commentedon Sep 1, 2012
I'm going to take this one, since @msullivan already has plenty of stuff ;-) I'm still getting the "incompatible type parameters" message too, which seems wrong. I'll keep looking.
Fix FIXME that's no longer blocked by #2611
vec: rm old_iter implementations, except BaseIter
Auto merge of rust-lang#2611 - pfmooney:libffi, r=RalfJung
Auto merge of rust-lang#2611 - pfmooney:libffi, r=RalfJung
Merge pull request rust-lang#2611 from Kobzol/gcc-unify
Merge rust-lang#2611