-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
bounds in iface types do not appear to be resolved #2311
Comments
ghost
assigned marijnh
Apr 27, 2012
ghost
assigned catamorphism
May 17, 2012
reassigned to me |
Is this intentionally still not meant to work for classes? iface clam<A> { }
class foo<A> {
new() {}
fn bar<B,C:clam<A>>(c: C) -> B { 1 }
}
fn main() { } Results in "unbound path clam". |
I'll take a look. |
punting to 0.4, but feel free to fix it for 0.3 anyway |
@z0w0 : This test appears to have been fixed too, probably as part of the move to resolve3. I added the test and am closing this. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
./miri many-seeds: also print the seed before we try it When using `cargo miri`, we otherwise have no way of even seeing which seed it is currently on.
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
Fix small issue introduced by rust-lang#2311
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
It looks like the other changes done by rust-lang#2311 to the release docker file were not as harmless as I thought. This change reverts them to fix the release action.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test, for example, yields the message "unbound path clam":
The text was updated successfully, but these errors were encountered: