Date: Thu, 25 Jun 2026 15:43:14 +0200
On 6/25/26 15:33, Rune Lund Olesen via Std-Proposals wrote:
> The current std::byte has some deep issues
Oh, yes. Before std::byte, there were three different ways to represent
an raw byte in memory: char, unsigned char, and uint8_t (almost always
an alias for unsigned char in practice), which is two too many. With
the addition of std::byte, there are now four, which is worse. And
that's not even considering that void * is also functionally a pointer
to a raw byte in memory.
But adding fifth one is just a repetition of the mistake that is std::byte.
> The current std::byte has some deep issues
Oh, yes. Before std::byte, there were three different ways to represent
an raw byte in memory: char, unsigned char, and uint8_t (almost always
an alias for unsigned char in practice), which is two too many. With
the addition of std::byte, there are now four, which is worse. And
that's not even considering that void * is also functionally a pointer
to a raw byte in memory.
But adding fifth one is just a repetition of the mistake that is std::byte.
-- Rainer Deyke - rainerd_at_[hidden]
Received on 2026-06-25 13:43:23
