Skip to content
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

Closed
nikomatsakis opened this issue Apr 27, 2012 · 5 comments
Closed

bounds in iface types do not appear to be resolved #2311

nikomatsakis opened this issue Apr 27, 2012 · 5 comments
Labels
A-resolve Area: Name resolution
Milestone

Comments

@nikomatsakis
Copy link
Contributor

This test, for example, yields the message "unbound path clam":

iface clam<A> { }
iface foo<A> {
   fn bar<B,C:clam<A>>(c: C) -> B;
}

fn main() { }
@ghost ghost assigned marijnh Apr 27, 2012
@ghost ghost assigned catamorphism May 17, 2012
@catamorphism
Copy link
Contributor

reassigned to me

@z0w0
Copy link
Contributor

z0w0 commented Jul 8, 2012

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".

@catamorphism catamorphism reopened this Jul 8, 2012
@catamorphism
Copy link
Contributor

I'll take a look.

@brson
Copy link
Contributor

brson commented Jul 9, 2012

punting to 0.4, but feel free to fix it for 0.3 anyway

catamorphism added a commit that referenced this issue Jul 13, 2012
@catamorphism
Copy link
Contributor

@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
Labels
A-resolve Area: Name resolution
Projects
None yet
Development

No branches or pull requests

5 participants