expikr

> 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. >...

A new idea is to introduce "Builtin methods" to specific builtin types like `@Vector` or `@Complex`, to express one-off operations specific to the type, proposed in https://github.com/ziglang/zig/issues/17274#issuecomment-2026541337 How it might...

`@splat` in its current form is useful for pre-computing a reusable SIMD vector that will be applied many times. Using it as a one-off scaling operation results in the verbose...

https://github.com/gabdube/native-windows-gui/ A project like this for Zig would be great, the thinnest possible wrapper over winapi syscalls merely to make it idiomatic for Zig.

> Check out zigwin32: > > https://github.com/marlersoft/zigwin32 https://www.youtube.com/watch?v=HsnWZxrf5VE That's autogenerated though, not quite "adapting it to be idiomatic zig", and much larger in scope than making just the GUI subset...

With the `@Vector` built-in supporting arithmetic operators, it seems like the only usecase wanted not already covered is concise swizzling. The functionality of swizzling is currently achievable via `@shuffle`, which...

I'm having a hard time wrapping my head around the concepts involved. Is my understanding correct that the issue arises from wanting each prong to contain all of the operations...

The issue would be solved by moving the divider `` onto the same level as chapter items rather than being nested under the immediately preceding section level. I'd like to...

Turns out the fix is as simple as just moving the divider processing to the same spot as part titles, no change to the logic whatsoever.

I prefer this PR because it makes https://github.com/rust-lang/mdBook/pull/2069 much easier