Nathan V. Morrical

@kaizhangNV Going to try digging into this today. Sounds like there's not much left needed to get this done.

Going to dig a bit more into this today. We have a proposal to correct this issue here, but it needs updating to accommodate the newer Type pattern: https://github.com/shader-slang/spec/blob/main/proposals/017-shader-record.md

@jhelferty-nv I did get a working version of the proposal, however there was relatively strong pushback from Tess and Yong. The mixed reaction signals that the current proposal isn’t the...

Can the "Resource" and "Sampler" integers there be integers evaluated at runtime? Eg, ``` ResourceArray resArray; int loc = resArray.get(0); Texture2D t = resArray.get(loc); ```

> The red underline there means the type system is working as intended. A `Sampler2D` is not a `Resource` kind, so you shouldn't be allowed to get a Sampler2D from...

For some context, this is what I'm kinda forced into doing at the moment with Slang. I force users to include some code which inlines the below descriptor arrays, which...

It's also very frustrating to need to include texture1Ds and texture3Ds when more often than not, folks using my framework don't use them. I have to add in these placeholder...

> We can have different type of Resources in the ResourceArray, but you can't get a Resource handle from a Sampler array. > > This is because HLSL/D3D distinguishes a...

@redorav Is this feature still planned? I find myself frequently using HLSL's `any`, `all`, `select`, `or` and `and` intrinsics with vector bool components. It would be really helpful for adoption...

Really, I’m aiming for a framework where I can share _slang_ code with the host. I agree that the direction HLSL went with this is frustrating… In slang, both &&...