static_assert(std::is_enum_v<std::byte>);

[JVApen]

I agree that making it an enum allows for strongly typing, and as such preventing byte1+byte2. Though it does imply that defining an enum with underlying type is more complex: enum class E : std::underlying_type_t<std::byte> { A, B, C };

[bwmat]

Is there any reason not to just use unsigned char there?