Vasiliy Tereshkov

Fixed `printf()` with `SetConsoleOutputCP(CP_UTF8)`. It still fails on Chinese characters, but at least prints Cyrillic correctly.

I fixed Chinese by changing the console font to `SimSun-ExtB`. Cyrillic characters look weird after that, but it's a decades-old font rendering problem: 

@skejeton Perhaps you're right, but the benefit-to-cost ratio is low, so I'm reluctant to do anything with it now.

It seems that the problem has been fixed in `cmd.exe` in Windows 11: ``` // test.um import ( "std.um" "utf8.um" ) fn testStr(s: str) { printf("string: %s\n", s) printf("bytes: %lld\ncharacters:...

Technically, this behavior is correct: 1. `alias1` and `alias2` are not equivalent (as they have different identifiers), but compatible (both are integer types) 2. `[]alias1` and `[]alias2` are neither equivalent,...

> []alias1 and []alias2 are actually trivially compatible, since they're technically the same type. What you mean here is that `[]alias1` and `[]alias2` are equivalent. Then `alias1` and `alias2` should...

@skejeton And thus you end up with a contradiction. > Having type assignments be base types will break a lot of things... so more logical thing for them is to...

@skejeton Are `[]alias1` and `[]alias2` different base types?

@skejeton Both `struct` and `[]` are the ways of constructing new types from existing ones. However, you seem to insist that a different rule be applied to `struct` than to...

@skejeton Now I understand you. Which doesn't mean I share the same view. 1. You essentially introduce a new (and not very easy to grasp) concept to the language, i.e.,...