-
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
Confusing error with :: on struct #10551
Comments
The "!!!" lines should be internal debugs, not user printouts. Adding a pull request to fix this, but not sure if any additional behavior here needs to be fixed. Are there existing instances where the Rust compiler warns you if you attempt to use a C++ OOP feature? |
Fixed by #11623. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Apr 6, 2023
In uninit checking, add fallback for polymorphic types After rust-lang#10520, we always assumed that polymorphic types do not allow to be left uninitialized. But we can do better, by peeking into polymorphic types and adding a few special cases for going through tuples, arrays (because the length may be polymorphic) and blanket allowing all unions (like MaybeUninit). fixes rust-lang#10551 changelog: [uninit_vec]: fix false positive for polymorphic types changelog: [uninit_assumed_init]: fix false positive for polymorphic types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code was my incorrect attempt to explicitly specialize a static method:
In fact, apparently the fn is not yet possible to call at all. However, the error output is needlessly confusing with an error!() message and three errors:
The text was updated successfully, but these errors were encountered: