If vkd3d_shader_descriptor_info1 is the way we're going,
And having given it some thought, I'm not quite convinced that this is what we should do. In particular, using vkd3d_shader_descriptor_info1 implies making vkd3d_shader_uav_flags visible as part of vkd3d_shader_descriptor_info_flag, as can be seen in !416 in particular. And while the two flags introduced by that MR seem innocuous enough, it does make it hard for me to see how this approach could be made to scale to DCL_* instructions in general.