Robin Voetter

Which function does this apply to? I checked them all and they seem to have the right parameter.

This is weird. There is no indication anywhere that this should be loaded by the `vkGetInstanceProcAddr`, and in [amdvlk](https://github.com/GPUOpen-Drivers/xgl/blob/b7100c18eb2d134098738f97d7cc3a26e485862f/icd/api/strings/entry_points.txt#L380) `vkSetDebugUtilsObjectNameEXT` seems to be a device-level function. Which driver and version...

> how to expect a certain switch prong ```zig switch (@expect(123, x, 1)) { 123 => { // likely }, 124, else => { // unlikely }, } ``` Here...

Wow sorry, I completely missed this issue. Considering that this is mostly just a light-weight wrapper, I think there is no downside into making these function inline (there shouldn't be...

Hmm, these were previously supplied by the user. Fyi, there are probably done other types that are broken like this. I wonder why the stuff to define them isn't being...

As far as I can see, these types are still generated. Furthermore, this is actually intentional. The vulkan-zig definition for these types is as follows: ```zig pub const CAMetalLayer =...

Indeed, these were not a thing when vulkan-zig was initially made. Seems like a good idea, though there will be a slight incompatibility between dispatchable and non-dispatchable handles. I don't...

I just want to highlight that LLVM bitcode is not stable, so this will add friction for the user. Is the plan to still have integration with clang, but via...

I used this project on the implementation of my bachelor's thesis, which is about ray tracing volumetric models with Vulkan (https://github.com/Snektron/Xenodon). Im happy to report that performance more than doubles...

 nobody `@expect`s the Spanish inquisition!!