Date: Fri, 26 Jun 2026 07:10:30 -0700
On Friday, 26 June 2026 01:15:23 Pacific Daylight Time Rune Lund Olesen wrote:
> 2. In generic code, while you can actually bitshift a std::byte, it eg. acts
> as an enumeration type and returns false with std::is_integral,
> std::is_fundamental, and so on - highlighting a few issues with using it
> with generic code 3. The idea to have a type to correctly represent "raw
> data" is good - it is the design or implementation if you will, that is
> lacking, and it should interop easier with other things (like conversions)
> and work better in generic code - right now it it way too restrictive and
> cumbersome, to the point it is prohibiting adoption.
I believe the main roadblock to adoption is that unsigned char is still there
and *is* the byte type.
> 2. In generic code, while you can actually bitshift a std::byte, it eg. acts
> as an enumeration type and returns false with std::is_integral,
> std::is_fundamental, and so on - highlighting a few issues with using it
> with generic code 3. The idea to have a type to correctly represent "raw
> data" is good - it is the design or implementation if you will, that is
> lacking, and it should interop easier with other things (like conversions)
> and work better in generic code - right now it it way too restrictive and
> cumbersome, to the point it is prohibiting adoption.
I believe the main roadblock to adoption is that unsigned char is still there
and *is* the byte type.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Received on 2026-06-26 14:10:38
