-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Remove mention of ~T in the FFI guide. #16393
Conversation
By the way, do we have the nullable pointer optimization for any of the library pointer types now? |
Presumably |
It does; the removal of |
@@ -527,8 +527,8 @@ the `libc` module, and Rust links against `libc` and `libm` by default. | |||
# The "nullable pointer optimization" | |||
|
|||
Certain types are defined to not be `null`. This includes references (`&T`, | |||
`&mut T`), owning pointers (`~T`), and function pointers (`extern "abi" | |||
fn()`). When interfacing with C, pointers that might be null are often used. | |||
`&mut T`), and function pointers (`extern "abi" fn()`). |
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.
The comma on this line is no longer appropriate, as the list now only has 2 elements.
@SimonSapin can you fix the problem @kballard has pointed out? |
@kballard, @steveklabnik: how is this? |
Sorry, I should have mentioned that they're called 'boxes', not 'owning pointers.' After that, |
@SimonSapin ping! |
Ugh. Updated. |
❤️ thank you! |
No description provided.