-
Notifications
You must be signed in to change notification settings - Fork 13.3k
bounds in ty params can't seem to refer to other ty params #2611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Adding (xfailed) test case as run-pass/issue-2611.rs |
Post-0.3, the test case gives this error instead:
Not sure whether or not the message is accurate, but it's certainly unhelpful. |
I'll try fixing the error message. |
Now it fails with a message saying they have incompatible type parameters. I think I'm going to look into this some. |
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. |
The removed test for issue #2611 is well covered by the `std::iterator` module itself. This adds the `count` method to `IteratorUtil` to replace `EqIter`.
Update libffi-sys to 2.0.1 Prior version of libffi [could not be cross-compiled to illumos](tov/libffi-rs#59) due to host-triple complications. This should fix rustup builds of miri for the illumos platform.
Update libffi-sys to 2.0.1 Prior version of libffi [could not be cross-compiled to illumos](tov/libffi-rs#59) due to host-triple complications. This should fix rustup builds of miri for the illumos platform.
This is more-or-less taken from commented-out code in core::iter-trait:
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.The text was updated successfully, but these errors were encountered: