zzyxyzz
zzyxyzz
I agree with @ifreund and @Hejsil, this looks like correct `undefined` behavior. The semantics of undefined, as inherited from C/C++, is that the bits are not only random, but *random...
`[4]vec i32` looks nice. Though maybe it should be `[4]simd i32`? To more explicitly signal that it is an array-like object that is meant specifically for SIMD processing. I know...
@LemonBoy, could you clarify? I was thinking of `[N]vec` as an atomic modifier just like `const`, `[N:0]` or anything else.
Some more syntax variants on a slightly more complex example: ```zig [w][h][4]vec f32 [w][h][4v]f32 [w][h][4 simd]f32 [w][h][|4|]f32 [w][h]@Vector(4, f32) ``` All of the bracket-based variants have the disadvantage that they...
Yeah, I guess the associativity is backwards in this case :smile:
`[4x]T` anyone?
Interesting question. From my *superficial* understanding of ARM-SVE, it represents a very significant departure from the SIMD paradigm. It is designed to operate directly on large arrays with runtime-known length,...
The main objection against the otherwise popular `f32x4` seems to be that it cannot express vectors of pointers. But since this is the only "non-standard" case that needs to be...
```zig const buffer_len = 2 * (N - 1); // ... more code fill_buffer(buf, len, 1); // hint: ought to be buffer_len ``` ``` > error: unused local constant `buffer_len`...
I think `bitfield` would have been ideal, if it weren't for the analogous `bitunion`, which is quite terrible. Maybe the same clarification value can be achieved by renaming `packed` to...