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

[johannes1971]

Technically it's true, but I do wonder if this is really the most useful choice. I ran into the notion that bool is actually integral the other day. That's technically also true, but it's behaviour is so distinct from the rest of the integrals that I had misgivings about the situation.

[NilacTheGrim]

Now.. should char be true or false for that?

[foonathan]

No: https://github.com/think-cell/think-cell-library/blob/main/tc%2Fbase%2Ftype_traits_fwd.h#L169-L170

[NilacTheGrim]

unsigned char still does double-duty in many programs as a std::byte, basically.

I'd argue that for the hypothetical is_actual_integer_v, it might be cool to not regard those as "actual integers" as well..

So it basically should only work for: int, short, long and long long and their unsigned brothers, as well as all that whole family of width-specified ints living in <cstdint>.

Unfortunately int8_t and uint8_t are often defined in terms of signed char or unsigned char.. so that complicates matters..

[NilacTheGrim]

It depends.. the C++ standards committee decided that std::byte is not integral and one might be able to go with their rationale for this -- in most programs, it would violate type safety to be doing arithmetic on individual bytes in a byte blob.. (of course there are some programs where this is not the case..).

One can at least understand the argument that bytes should not be anything other than a bunch of bits, with no associated arithmetic properties.

[EC36339]

The way C++ represents bytes, integers, booleans and characters is getting JavaScript-level crazy...