And also is somewhat misleading in that for someone primarily developing on dx12 and does not properly set shader stage flags, their code won't run properly on vulkan/metal. Vulkan panics and gives proper validation error, metal seemingly doesn't complain but will give wrong output.

Fair enough but handling all sort of invalid usage is not really in scope of the library. This means specifying for example VERTEX | FRAGMENT as shader visibility flags and using the descriptor in a geometry shader will still work fine for dx12 after addressing the issue.

Of course, just thought it was funny to see this issue posted when I'd helped someone debug this issue literally last night ;p

yeah, I skimmed over the discussion 👀

Guideline:

1. Identify all occurences of ShaderVisibility::All in the code (e.g https://github.com/gfx-rs/gfx/blob/master/src/backend/dx12/src/device.rs#L1326)
2. Write a mapping function from Vulkan's shader stage flags (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/man/html/VkShaderStageFlagBits.html) to D3D12s visbility flags (https://docs.microsoft.com/en-us/windows/desktop/api/d3d12/ne-d3d12-d3d12_shader_visibility)
3. Apply mapping to all occurences