Theresa Foley

As for the bigger questions around the reflection API, part of the issue is that the surface area for reflection is very large and the API has evolved over time...

(Apologies if any of this is redundant given code you've already written. It might still be helpful to anybody reading through issues later on to try to learn things) In...

Yeah, there's a lot of trade-offs in designing a reflection system for shader code. A lot of times what an individual user wants is just a bunch of flat lists...

We don't currently support SPIR-V specialization constants as part of layout. I don't think it would be especially difficult to support them in a simple fashion, and we'd definitely accept...

Sorry for the slow turnaround on some of this. I have been juggling a few different things related to this project that aren't visible on the public GitHub. I don't...

We would welcome work on adding some level of support for ray tracing (whether DXR 1.0 / `TraceRay` style or DXR 1.1 / `TraceRayInline` style) on CPU. We don't currently...

Thanks for providing a repro for the issue. I haven't had a chance to debug this yet, but from the error messages it seems that the GLSL output that Slang...

Are you able to debug this issue more and work toward a fix? If so, that is probably the easiest path forward. If you don't think you have line-of-sight to...

You are right that it would make some sense to have the CPU C++ path change in the same way. I'm not especially concerned about the performance implications for CPU,...

As I dig into the problem of getting `extension`s of an interface to apply to concrete types implementing that interface, I’m realizing that we kind of want to treat an...