Mateusz Kielan

Alternatively if the compiler instantiated "reference meta types" like suggested in #4986 then you could add the layout rules as a template parameter to later work out the `OpAccessChain`

ok this is quite strange as @llvm-beanz says that what's going on under the hood https://github.com/microsoft/hlsl-specs/issues/24#issuecomment-1372813829 is that in DXC (which is a fork of llvm 3.7) the `float` and...

> or any sort of non-trivial code the reuse is minimal. If you can provide a real world use case for this (not just that it can be done and...

> I've also always accomplished that via defines to the shader compiler, which you probably need to pass in anyway to select them between two shaders that do different BRDFs,...

At the end of the day whether you explicitly specialize your templated struct, or write out separate ones and template their aliases, it doesn't matter. You'd probably want to use...

> I'd love to be able to include it in my project for some of the glsl built-ins, but this is a little too large for me to casually include...

> > @expenses current nice solution would be to do shallow clone, you will reduce the size to 6.19 MiB > > Ah, that's a great solution, I totally forgot...

ok there's a lot of options in our CMake now to control shallow vs deep submodule checkout also we don't recursively clone all submodules anyway

Its now broken in new and fun ways https://godbolt.org/z/onYcs95bc ``` fatal error: generated SPIR-V is invalid: Structure id 7 decorated as Block for variable in PhysicalStorageBuffer storage class must follow...

> Its now broken in new and fun ways > > https://godbolt.org/z/onYcs95bc > > ``` > fatal error: generated SPIR-V is invalid: Structure id 7 decorated as Block for variable...