-
Notifications
You must be signed in to change notification settings - Fork 13.4k
libcore: Get rid of useless mem::forget wrapper. #16509
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
Conversation
@@ -19,6 +19,16 @@ use ptr; | |||
|
|||
pub use intrinsics::transmute; | |||
|
|||
/// Moves a thing into the void. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these docs (and even the #[stable]
) may need to go on the actual definition, not the reexport.
(@aturon would know for sure about the reexport.)
Do intrinsics seamlessly cast to rust functions yet? This is a breaking change if not, and one I have argued against several times. How does rustdoc deal with this? |
Poorly, e.g. |
I see transmute has been done. I think we should consider it a bug if this exposing special rust-intrinsic semantics. |
Yes, I agree with @brson that this needs to be a I do think, however, it's ok to land for now. RFC 5 will give intrinsics the same ABI as other rust functions, so it is going to be fixed on the horizon. |
I also agree it's ok to land as long as we're in agreement there are bugs. |
@bors seems to have not noticed the r+ here, but @alexcrichton did ask for a [breaking-change] tag. |
fix: Fix tuple structs not rendering visibility in their fields Fixes rust-lang/rust-analyzer#16508
Fixes #15401.