Date: Thu, 25 Jun 2026 08:18:36 -0700
On Thu, Jun 25, 2026 at 6:34 AM Rune Lund Olesen via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> Hello All,
>
> The current std::byte has some deep issues in that it is too opaque to the point it is flawed by design.
> (we know it is in reality a scoped enum).
I don't accept the premise (or at a minimum, it is an unsupported
premise). Could you please elaborate on what the problems are first?
Why existing solutions are insufficient, and how whatever you're
suggesting solves the problems.
> Especially this comes up in generic code where it is cumbersome to add specializations because it is not a fundamental type.
Example, please.
<std-proposals_at_[hidden]> wrote:
>
> Hello All,
>
> The current std::byte has some deep issues in that it is too opaque to the point it is flawed by design.
> (we know it is in reality a scoped enum).
I don't accept the premise (or at a minimum, it is an unsupported
premise). Could you please elaborate on what the problems are first?
Why existing solutions are insufficient, and how whatever you're
suggesting solves the problems.
> Especially this comes up in generic code where it is cumbersome to add specializations because it is not a fundamental type.
Example, please.
Received on 2026-06-25 15:18:55
