ndk/hardware_buffer: Convert HardwareBufferUsage
to bitflags
#461
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.
HardwareBufferUsage
really is a structure that comprises various usage flags, and was modeled as a hard-to-getu64
value while being wrapped inside two newtypes (one in thendk
, one inndk-sys
) and without the typical bit-ops (i.e.BitOr
) one comes to expect.This is all provided out of the box - and more helper functions - via
bitflags
with more convenient access to the raw value to beat.Also inherit the upstream docs for convenience and completeness.