-
Notifications
You must be signed in to change notification settings - Fork 9
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
ManuallyDrop causes pinning to be unsound? #52
Comments
Some more IRC chat: https://botbot.me/mozilla/rust-lang/2018-02-01/?msg=96382526&page=2 |
And yet more, this time with a possible solution! https://mozilla.logbot.info/servo/20180201#c14230291 |
A very rough draft of what a fixed API would look like: https://play.rust-lang.org/?gist=6791dbfd630b20c8cabda5511e43e089&version=stable |
Posted a "lessons learned" message to the unsafe code guidelines discussion forum: https://internals.rust-lang.org/t/rust-1-20-caused-pinning-to-become-incorrect/6695 |
ManuallyDrop<Pin<T>>
causesPin<T>
not to call its destructor, oh dear. This is different frommem::forget(T)
because that has to be called after the pinning (so the borrowchecker will complain about lifetimes) whereasManuallyDrop::new
is called before. Sigh.The text was updated successfully, but these errors were encountered: