refactor: Have ArrayBuffer::data
return Option<NonNull<c_void>>
#1131
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.
The pointer returned by
ArrayBuffer::data
might be null if the backing store has zero length, but the return type*mut c_void
does not force the user to consider this case. This change makes the return typeOption<NonNull<c_void>>
, which is semantically equivalent, but which forces users of the API to handle theNone
case.This PR is the
ArrayBuffer
counterpart to #817.This is a breaking API change.