expikr

> > > > > As a Windows-based user, I am now filled with envy, jealousy and anticipation. > > > > > > > > > > > >...

Why not just make a single builtin that specifies behaviours explicitly, considering that it's basically two separate steps/operations being shoehorned into one? ```zig fn intFromFloat( x: anytype, comptime underflow: enum{...

What is currently exposed in love.dll? A first step could be to document an unstable "as-is" ABI for those looking to "hack" functionality anyways willing to work around quirks.

It seems that even with v3.4's smoothscroll enabled, the scroll steps are still being accumulated to a threshold then fired like a normal scrollwheel, rather than reacting to the individual...

Can multiple unused fields use `_` as their field name provided that they have a default initialization value?

Equivalent to ```zig const B = struct { pub fn func() void { @compileLog(@typeInfo(C).Struct.decls); // .{ .{ .name = "func" } } @compileLog(@hasDecl(C, "func")); // false _ = C.func; //...

`bits {...}`

```error: namespace variable contains reference to comptime var``` or ```error: container-level variable contains reference to comptime var``` or ```error: runtime value references comptime var```

@squeek502 related to https://github.com/ziglang/zig/pull/17763 ?

> I like this interface even more: https://github.com/ziglibs/zlm/blob/master/src/zlm-generic.zig#L139 > > ``` > /// Examples: > /// - `vec4(1,2,3,4).swizzle("wzyx") == vec4(4, 3, 2, 1)` > /// - `vec4(1,2,3,4).swizzle("xyx") == vec3(1,2,1)` >...