Firstly, I guess you state these aren't built in yet, so I guess it might change, but I wonder if the lack of unsigned primitive types is intentional? It seems

Firstly, I guess you state these aren't built in yet, so I guess it might change, but I wonder if the lack of unsigned primitive types is intentional? It seems like something I would want to be built in. Secondly, you have byte as int8 and char as int8 - in reality, either could be unsigned surely? For me, byte is unsigned. As I mostly do C# these days, char is not generally used as a numeric value also. It feels like - if you have byte, char can represent an actual character value. But it feels like not making char multibyte (UTF8 would work) it makes your typing system need to deal with all the WChar nonsense/legacy. Better to just make it UTF8 now? If you don't have byte, I guess you can have char, but that feels like more legacy.