1. Right now, you can emulate this with the transmute builtin function. Not yet sure if the additional complexity of this feature would be worth it.
2. Array bounds checks can be avoided by using the unchecked_index builtin. Uninitialized locals are not yet possible, but I think it makes sense to eventually add a construct to allow that, for situations that need every last bit of performance.
3. I've only started to look into LLVM recently, thanks for the heads up.
4. See my comment here: https://news.ycombinator.com/item?id=19599908
5. C# programmers would like to disagree with you ;). Note that the formatting issue is not due to significant whitespace, as you'd have the same issue writing up a Golang snippet.
6. Editor support (specifically, language server) should help a lot here.
7. The string based types are only used for inserting the right cast to make the C compiler happy, so they should not be an obstacle.
8. Compile time evaluation can be used for some cases. Adding a preprocessor comes with its own set of tradeoffs, haven't yet decided what to do there.
9. A lowercase l looks a lot like a 1 in many fonts, hence the uppercase L. Will consider adding an i suffix.