extensions/ext: Add VK_EXT_extended_dynamic_state3

[MarijnS95]

Depends on #667, cc @wrightwriter

[coffeenotfound]

When is this going to be merged? I would really need ext_dynamic_state3

[MarijnS95]

@coffeenotfound Whenever it receives review.

[wrightwriter]

i'm wondering if it makes sense to have the dynamic state extensions as a traits on device.

[MarijnS95]

Hardly any of the functions take a VkDevice, I think you're more so intending this to be on VkCommandBuffer.

Unless you're intending for a model where ash::Device loads and stores all device functions, including all extensions, I think Erupt does something like that.

[wrightwriter]

Ok, my logic was that core vkCmd are on the device. But what you are saying makes sense.

[MarijnS95]

Most of these functions are loaded for a device (and vk::CommandBuffer is a special child specific to a single vk::Device), and all the standardized .cmd_ function are hence loaded for and available on a device.

The main point is that we didn't force this for extensions, so that the ash::Device object doesn't get too bloated with all extensions and their optionally-loaded/available functions.