On Wed Feb 21 17:26:35 2024 +0000, Jacek Caban wrote:
Are you sure about that? I don't see it explicitly prohibited and it doesn't seem to cause problem in my testing. This code could use a bit more sharing between code paths, so I refactored it and avoided duplicates, but there is a similar thing in `wine_vk_instance_convert_create_info` (in which we probably want to make `VK_KHR_external_memory_capabilities` optional now).
That comment was meant as a reply to duplicated extensions comment.
For `vk_is_available_device_function`, that's right (and that doesn't seem too problematic). I was thinking that ideally we'd just get rid of `vk_is_available_device_function`. We could store enabled extensions in VkDevice_T and implement `vkGetDeviceProcAddr` based on that, without any Unix calls.