-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Check the bounds in impls against concrete types #16955
Milestone
Comments
Nominating because it is a backwards incompatible change |
Turns out this only affects impls with no trait, we already do the expected thing if there is a trait. Example,
Should not type check. |
nrc
added a commit
to nrc/rust
that referenced
this issue
Sep 5, 2014
bors
added a commit
that referenced
this issue
Sep 6, 2014
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 31, 2024
…lnicola fix: check for client support of relative glob patterns before using them Fixes rust-lang#16955
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
E.g.,
impl<X: ...> Trait<X> for Struct<X> { ... }
we check the bounds ofX
satisfy the bounds given byTrait
, but not those given byStruct
. I don't think this is a soundness issue (because any use ofX
is limited to the impl and relies on the given bounds, not the bounds given byStruct
), but it is a bit odd and not the behaviour I would expect, especially given RFC 11 (https://github.com/rust-lang/rfcs/blob/master/active/0011-bounded-type-parameters.md).The text was updated successfully, but these errors were encountered: