Rua

Development of Vulkano mostly stalled shortly after the release of Vulkan 1.1, so it is lacking many newer features, including timeline semaphores. I've been trying to get things up to...

Vulkano needs to support all Vulkan versions, so we can never completely get rid of binary semaphores. But `Future` should use timeline semaphores if they are available. So there would...

I just dug into the RADV sources in Mesa, which handle the userspace side of Vulkan for AMD for Linux. And it turns out [here](https://gitlab.freedesktop.org/mesa/mesa/-/blob/master/src/amd/vulkan/radv_cmd_buffer.c#L5114), resetting a command pool actually...

@AustinJ235 is this still a problem for you?

Are you using the `shaderc-build-from-source` feature? I think that shouldn't happen without that feature enabled. If it's happening anyway, then that seems like a bug.

@ShaunKulesa is this still an issue for you?

Does this issue still occur with the latest Vulkano?

Your second point already exists, it's the `descriptor_layouts` method on the `ImageAccess` trait. It doesn't contain all the items you mentioned, but the basic idea is there. I've been thinking...

Clearly these need to have different names, but what should they be?

What about the names `A` and `B`? How come those aren't used by Vulkano-shaders?