Planet Chili

You need to read up on pointer decay of arrays. https://stackoverflow.com/questions/1461432/what-is-array-decaying you don't pass arrays by value, they become pointers. If you wanna avoid that, use std::array<std::array>, or pass the array by reference. Passing by reference will lock you down to a s...

The problem, is this.

Yup, you clacked the wrong place and set up a breakpoint by accident

If you're really buttfucked over this one, just skip over to Tutorial 7 and you'll learn about what this shit is all about.

Can't stop, won't stop.

Did you copy that code or like type it out again. Because privare is not a C++ keyword

Idk about too many temporaries. I guess the best way is to write up something minimal and examine the output in Godbolt.

It was probably a slight missed opportunity there to not better mimic the constant buffer arrangement of hardware APIs.

Theoretically I guess it seems possible. Mostly it's probably just really hard to implement. Constraining what can and cannot be executed at compile time makes the implementer's job attainable, and adding the constexpr keyword enables the compiler to verify that your intentions are possible to carry...

So dilemma number one is: Seeing as how each one of these operations is going to take parameters by *value, calling each one will create copies before executing the intrinsic used inside each function, so is it even worth the effort to create such a library? I wouldn't assume that just because para...

Doing some SIMD stuff again I see