Christoffer Lerno

File an issue for that, because it seems like an omission.

Also related: #1388 #1585. Short story is that it builds by grabbing the *static* LLVM libraries from Homebrew. But those are idiotically built with *dynamic dependencies* to other homebrew packages....

Arguing for other type names is common, see https://github.com/c3lang/c3c/issues/1566 https://github.com/c3lang/c3c/issues/1178 https://github.com/c3lang/c3c/discussions/1681 https://github.com/c3lang/c3c/discussions/434 https://github.com/c3lang/c3c/pull/2072 https://github.com/c3lang/c3c/issues/660 People from Rust wants i32/u32/isize/usize, people from Nim or Swift wants int32/uint32 etc. There are strong...

Also note that for C the only way was to introduce int32_t and so on. It couldn't very well suddenly bit-fix existing names! Also, people tend to forget that stdint.h...

I do take suggestions on how to improve the more ad hoc names: `ichar`, `int128` and `uint128`. However, on the large we're sticking with C#/Java C-names-with-fixed-bitsize.

This should work properly now. There was further problems when hiding bools and bitstructs behind typedefs as well. It works for the test cases I've added, but maybe there is...

This could possibly be done using the same mechanism as getting all members, except there is no "set" method for it.

This is now available: ```c enum Foo : (String x, int val) { ABC = { "Hello", 3 }, DEF = { "World", -100 }, } fn void main() {...

Please try it out.

The problem is that this is currently printing things out of order. Note that having [current/failed] rather than [passed/total] is essential for being able to narrow down issues with CI,...