@pezcode Do you have a good idea how to fix the object_type errors? I experimented a little with macros but without success.

Perhaps we can come up with a good solution. These Vulkan defines are really annoying.

Ugh, this mess... I don't think this is 'fixable' without creating your own wrappers for objects (for example, this is what bgfx does), but then all code would have to use those, and that's just not fun...

Practical suggestion: disable the automatic type deduction on Win32 altogether and only expose the functions with the manual VkObjectType parameter. Either with an ifdef (vulkan_core.h sets VK_USE_64_BIT_PTR_DEFINES to 0 or 1 depending on whether it's uint64_t or a unique type) or some SFINAE magic.

Thanks for your input - thought the same way: all not nice

That is why I go for a verbose approach: set_x_name and set_x_tag

Fortunately, we have a specification that remains relatively stable 🙏