3 ms·
This seems wrong. Regardless of what char8_t is, doesn't char* have a spec-given right to read it? Defining char8_t as a new type is specifically to avoid unne
by arc-in-space 5y ago
This seems wrong. Regardless of what char8_t is, doesn't char* have a spec-given right to read it?
Defining char8_t as a new type is specifically to avoid unnecessarily granting it these all-aliasing powers, but you can still read it as bytes.
- Kranar 5y agoYes, but as I mentioned earlier only char* has the right to read it, in the snippet I posted, it's char8_t* doing the reading.