-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Classes: test that classes can implement parameterized ifaces #2288
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
Labels
A-type-system
Area: Type system
Milestone
Comments
catamorphism
added a commit
that referenced
this issue
May 7, 2012
Necessary to resolve any type arguments in a ref to a parameterized iface. This meant that, for example: class A implements B<int> { ... didn't work before, because the "int" in B's argument wasn't getting visited, and thus wasn't getting resolved. Now it works. Partially addresses Issue #2288, but I also want to check that class ty params can appear as the type arguments to ifaces (for example, class A<T> implements B<T> {... should work.)
I found this wasn't really working at all. More-or-less fixed in a3be0b1, probably bugs still remain. @catamorphism I am 99% sure what I did was right, but lemme know if you disagree. |
This seems to work. Added a test case, closing; open new bugs if there are issues. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
add ./miri clippy also make ui_test comply with clippy
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
Signed-off-by: Felipe R. Monteiro <felisous@amazon.com>
jieyouxu
added a commit
to jieyouxu/rust
that referenced
this issue
Apr 2, 2025
…akes-args mention that known-bug test directive takes arguments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This probably doesn't work right now.
The text was updated successfully, but these errors were encountered: