tecanec

Chapter 2 is way too long and non-specific. Splitting it up into a "Standard Patterns" folder could help people like [this guy](https://github.com/ziglang/zig/issues/8645), who just want to know how to perform...

> You know what's really pleasant to work on? The build system. Well, that explains it... > The lazily built executables can take full advantage of native CPU features. We...

I'd suggest taking this a step further, actually: Replace `@shuffle` with `@swizzle` entirely and add a function to `std.simd` that the compiler can optimize into a shuffle instruction. In my...

> Reducing the capacity of a SIMD builtin seems explicitly like a step backwards. You can implement swizzling in terms of shuffling without losing performance, but the same is not...

I think I have another use case for `@expect`: Hot loops. Let's say we're making a loop which we want to iterate, say, a billion times per second, and for...

I agree heavily with this, and would even consider it a necessity. A fully Zig-compatible ABI is something we should have. As an example use case (if that's even needed),...