Wooster

It would be nice if we could keep the API as-is but if we end up doing that I would not make it optional though, like any other type parameter....

Yes, that's basically what it does. It's like applying that same alignment manually to every field in the struct.

1. I think `-q` is kind of conventional. One could expect a compiler to have this option, similarly to expecting `--color` to be an option. 2. I don't think `--color...

I fixed this PR and addressed my comment above; here's a conclusion: * `--color off` no longer turns off progress output but turns off color. * `TERM=dumb` turns off progress...

Mostly for performance. I compared the two and the imprecise method (unsurprisingly) is faster. You are definitely making a good point that the user may want precision over speed. Not...

FYI here you can see the differences in codegen: https://zig.godbolt.org/z/GPG8YG9qd Just go to the exported `main` and change the lerp for the one you want to test. C++'s way is...

That's not a bad idea either. But I think that name focuses a bit too much on speed over the fact that it's simply just a bit less precise. And...

Wow, thanks for bringing that up! That is one very interesting builtin that I haven't considered here. Have a look: https://zig.godbolt.org/z/qcMehj4jo `mulAddImpreciseLerp` is indeed the fastest here (I did some...

Now the lerp looks like this: ```zig std.math.lerp(f32, .{}, 0, 100, 0.5); // 50 ``` And in `.{}` you are free to alter the way it calculates.

Well I thought it'd be nice to offer more options for all kinds of cases but I guess it would be a ton simpler if there were only 2 options.