The VK_SEC_ubm_surface extension has conflicts between structure names, fields, and parameters.

[rosew0od]

There are two types, ubm_device and ubm_surface, that also appear as field and parameter names. This can cause problems for generators that don't generate a struct prefix for types.
The fields in VkUbmSurfaceCreateInfoSEC, and the parameters of vkGetPhysicalDeviceUbmPresentationSupportSEC should be renamed from ubm_device and ubm_surface to device and surface.
The Wayland surface extension has similar types wl_surface and wl_display and their respective parameters are named surface and display, which avoids this problem.

[spencer-lunarg]

@rosew0od I am not dismissing this issue here, but asking out of curiosity as we tend to not have any good way to know that kind of changes are breaking generators downstream. We created this vulkan_object python interface (even have a pip install module https://github.com/KhronosGroup/vulkan-object) and if you are able to use this, it can help shield you from things like this breaking like this. Is this something possible you could use?

[rosew0od]

@spencer-lunarg Thanks for the suggestion, it seems like vulkan_object provides the same information as the XML registry. Unless dropping the struct prefix from a type is unsupported, this doesn't seem like a usage problem.

[r-potter]

Thanks for raising this. I've opened an internal MR to rename these.

[oddhack]

This should be fixed in the 1.4.344 spec update. We've also added some CI checks to prevent it recurring in the future.