NULL safe set_boxed_mut_ptr/set_arc_mut_ptr #402
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously the `set_boxed_mut_ptr()` and `set_arc_mut_ptr()` helper fns used for assigning out parameters across the FFI boundary took `*mut *mut C` and `*mut *const C` for the destination argument `dst`. Using these safely required callers always verify that `dst != NULL`. In practice it's very easy to forget to do this and danger lurks! We could modify these helpers to do the check itself, but we tend to use these fns near the end of a function to assign a result in a success case and we would prefer `NULL` checking happen at the beginning of the function. One proposed solution is to modify these setter functions to take `&mut *mut C` and `&mut *const C`. By using new helper fns to carefully construct a `&mut` from the input double pointer we can front-load the `NULL` check and the assignment in the set fns can proceed knowing there's no possibility for a `NULL` outer pointer. This commit implements this strategy, updating the argument type of `set_boxed_mut_ptr` and `set_arc_mut_ptr` to take `&mut (*const|*mut) C`. New `try_mut_from_ptr_ptr` and `try_ref_from_ptr_ptr` macros allow converting from `*mut *mut C` and `*mut *const C` to the reference types, bailing early for `NULL`.
|
I think the fn names and rustdoc could use some bike shedding but I wanted to get this up for input before I log off. 💤 |
jsha
approved these changes
Mar 29, 2024
ctz
approved these changes
Apr 2, 2024
|
Thanks for taking a look.
#404 might be of interest in that area as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the
set_boxed_mut_ptr()andset_arc_mut_ptr()helper fns used for assigning out parameters across the FFI boundary took*mut *mut Cand*mut *const Cfor the destination argumentdst. Using these safely required callers always verify thatdst != NULL. In practice it's very easy to forget to do this and danger lurks!We could modify these helpers to do
NULLchecking, but we tend to use them near the end of a function to assign a result in a success case and we would preferNULLchecking happen at the beginning of the function.One proposed solution is to modify these setter functions to take
&mut *mut Cand&mut *const C. By using new helper macros to carefully construct a&mutfrom the input double pointer we can front-load theNULLcheck and the assignment in the set fns can proceed knowing there's no possibility for aNULLouter pointer.This commit implements this strategy, updating the argument type of
set_boxed_mut_ptrandset_arc_mut_ptrto take&mut (*const|*mut) C. Newtry_mut_from_ptr_ptrandtry_ref_from_ptr_ptrmacros allow converting from*mut *mut Cand*mut *const Cto the reference types, bailing early forNULL.Resolves #380