On Thu Nov 23 13:42:47 2023 +0000, Conor McCarthy wrote:
And, after all, if a shader requires it there is little that can be
done: we either enable it or fail; so we could directly assume it's available and generate a shader, and the execution environment will then decide whether that shader is usable or not One problem with this approach is Vulkan pipeline creation functions do not return errors; if they reject a SPIR-V binary they assert, so all the user sees is a crash. I'm not sure what the drivers will do if a binary uses 64-bit ints and they are not supported by the hardware, but crashing is one possibility.
Yeah, that's a sensible concern. At any rate, my feeling is that despite the name `extensions` is better suited for passing this kind of information.