Michael Mestnik

It shouldn't be a big deal, the `deprecated` `note` can easily reference the new name. The docs should contain a link and you can update any bookmarks. The thing is...

`deprecated` is not breaking... last I checked.

I think you are missing two important options. Don't upgrade ash and start using the new name.

`get_device_proc_addr()` feels like it should be callable from an `ash::Device`.

There is also higher level APIs that implement [auto-destroy](https://gitlab.com/cheako/ash-tray-rs/-/blob/master/src/vk_helper.rs) or treating CommandBuffers with different Queue properties as being separate rust types, to guard against calling unsupported cmd functions at compile...

Thinking about it, I don't know what cause PhysicalDeviceFeatures2 to ever be used as a branch. It can be, but it's main usage would be for get_physical_device_features2(). Afterwards DeviceCreateInfo.p_enabled_features ==...

I'm using `vi`, but the same task could be accomplished with a GUI using a configuration panel and a backend database(like a json or xml file). Most of the environment...

There is also something that I've never done, but [VK_ICD_FILENAMES](https://bityl.co/Dc2A).

This is extremely useful for all Vulkan applications, including DXVK. This would be useful to a smaller extent for both native and proton apps.

A setting of 2 is too big and a setting of 3 is worse. Any chance of changing the granularity to allow half steps? Also it's hard to adjust these...