-
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
"Static" methods should not be object safe #19949
Comments
I hope that fixing this doesn't cause another round of annoyed users. :( |
See #18527, the PR that introduced this, and rust-lang/rfcs#428, which is the same issue as this one. |
nrc
added a commit
to nrc/rust
that referenced
this issue
Dec 30, 2014
Closes rust-lang#19949 and rust-lang/rfcs#428 [breaking change] If you have traits used with objects with static methods, you'll need to move the static methods to a different trait.
This was referenced Dec 30, 2014
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Dec 31, 2014
Closes rust-lang#19949 and rust-lang/rfcs#428 [breaking change] If you have traits used with objects with static methods, you'll need to move the static methods to a different trait. r? @cmr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While reading the object safety code I found this:
I think this is sadly incorrect. The whole idea of object safety is to ensure that an object type
Foo
implements the traitFoo
. But if that is the case, then we can have an example like this one:cc @nick29581
cc @aturon
The text was updated successfully, but these errors were encountered: