John Kessenich
John Kessenich
A lot is missing at this level, but that is okay. No preprocessor, no constant folding, no implicit conversions, no overloaded function resolution under conversion, no OOP, etc. These all...
Sounds like most these questions are about tooling, but regarding location of the specifications, they are all kept in the SPIR-V registry, hosted by Khronos, at https://www.khronos.org/registry/spir-v.
Note that #2277 is still WIP, but now #2282 is not. Is there any dependency?
Originally shipped GLSL had already made the decision that `&&` and `||` were flow-control operators just as they are in C/C++. E.g.: ``` if (a > b || funcall()) ......
Or, generalize `&`, `^`, and `|` to also operate on vectors of Booleans. I don't know if it's worth adding the functionality or not. We also have `mix()`. I'm curious...
Agreed with adding built-in functions, if anything does get added. The macros are a good idea, but error prone if there are side effects, because they evaluate `b` more than...
It has never been implemented.
How are you building it? Or, getting it already built?
You should just need to build while targeting the right environment. MSVC has options (sometimes have to download and install?) to target other kinds of systems. I did that once...
Has anyone tried using Visual Studio 2019?