Replaced uint8_t with unsigned char in BYTE typedef for post C99/C++ #1581
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.
Uint8_t is not necessarily a typedef for char or unsigned char (or std::byte), for this reason, it can be undefined behavior to read or modify arbitrary data through it.
Ideally, we would select uint8_t anyway if it happens to alias one of the types permitted to read or modify arbitrary data, but I don't think it can be implemented without _Generic()
The types in header are commented as not part of public api so this should not result in ABI break for those who heed the warning. There is no such warning in the .c but I would presume that is only because it is taken for granted.