Properly handle u8 pointers when assigning and comparing #8818
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.
raw6() is one thing left over, we sometimes have
u8 scope
at the end so it is not techically valid code to reinterpret like that. alignment works out, thoughtbh I'd prefer we return a real value instead of pointer for our internal usage, and leave ptr access for Arduino compatibility (meaning, std::array<uint8_t, 4> and std::array<uint16_t, 8> / std::array<uint8_t, 16> and operate on that vs. weird overloads all over the place and no size checks)