Theresa Foley

The ability to write an `extension` that applies to an `interface` type is coming up as an important feature, and without it the demand for things like inheritance will only...

I think that the first version of `raw_cast` proposed here would probably be relatively easy to support if we could agree on some initial rules/restrictions: * The sequence of "leaf"...

I can try to take this one. It would be helpful to get a sense of timeline and/or urgency.

Apologies for the delay in responding to this. Overview ====== There's a lot to the question here, and I'd like to strike a balance between actually answering the detailed questions...

Apologies for the slow turnaround on this conversation. I don't know if there is a particular solution at the lower level that would be perfect for a node-based material/shader graph...

Update: we have been having some discussion about this issue as there is desire to get these types right for the GFX API sooner rather than later. The above proposal...

From conversation around this, it seems like our disposition for now is to issue a better error in cases where a user writes `` in a generic parameter list, since...

> Would it be desirable/possible to make bindless or not an external decision communicated to the compiler via the API? I mention this briefly (the second-to-last paragraph). I agree that...

This sounds really interesting and I do agree that there would be value in the compiler infrastructure being able to produce stable hashes that identify compilation requests. My naive thought...

At the time `import` got added, we didn't have `namespace` support, so that explains at least some of the problems here. It is worth noting that there are really two...