Would it make sense to reuse (part of) wined3d_context_vk_update_blend_state() here? Perhaps using some helper functions for state translation? Likewise for wined3d_context_vk_set_dynamic_rasterizer_state().
Possibly, though it'd result in at least redundant copies from VkPipelineColorBlendStateCreateInfo to VkColorBlendEquationEXT.
It's not necessarily pretty, but note that in principle something like this would work if we cared to avoid that particular issue: ```c VkPipelineColorBlendAttachmentState *a = ...; VkColorBlendEquationEXT *b;
b = (VkColorBlendEquationEXT *)&a->srcColorBlendFactor; vk_blend_equation_from_wined3d(b, ...); ```