VK_EXT_external_memory_metal validation
There are some UNASSIGNED VUIDs that I thought would be useful for the user but I'm not sure under which struct they should be. Any suggestions are more than welcome!
I believe there could be a best effort check on certain VUIDs that are not implemented like The memory from which handle was exported must have been created on the same underlying physical device as device but would require adding support for having Objective-C files in the repository, unsure if there's something like this at the moment (happy to learn if there's any so I can do some testing).
I believe there's a few missing tests for some VUIDs. I'll double check everything tomorrow. Just want to start getting some eyes into this so we can move it forward for extension release. Not looking for approval for merge since that can't happen until the extension is released.
CI Vulkan-ValidationLayers build queued with queue ID 249962.
CI Vulkan-ValidationLayers build # 17383 running.
CI Vulkan-ValidationLayers build # 17383 failed.
CI Vulkan-ValidationLayers build queued with queue ID 252306.
CI Vulkan-ValidationLayers build # 17412 running.
CI Vulkan-ValidationLayers build # 17412 failed.
CI Vulkan-ValidationLayers build queued with queue ID 263839.
CI Vulkan-ValidationLayers build # 17585 running.
CI Vulkan-ValidationLayers build # 17585 failed.
Extension being done here - https://github.com/KhronosGroup/Vulkan-Docs/pull/2414
Closing as this has got stale (and the rebase might be worse than restarting)