As a specific example, both the article and code contain the statement,
VkPipelineStageFlags waitStages = VK_PIPELINE_STAGE_2_COLOR_ATTACHMENT_OUTPUT_BIT;
However, this should either be:
VkPipelineStageFlags waitStages = VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT;
or
VkPipelineStageFlags2 waitStages = VK_PIPELINE_STAGE_2_COLOR_ATTACHMENT_OUTPUT_BIT;
(with cascaded changes VkSubmitInfo -> VkSubmitInfo2, etc..)
This is not the only place where "legacy functionality" is used in the code and article. What should be done, both with this specific case, and as a policy for the entire repository?
As a specific example, both the article and code contain the statement,
However, this should either be:
or
(with cascaded changes
VkSubmitInfo->VkSubmitInfo2, etc..)This is not the only place where "legacy functionality" is used in the code and article. What should be done, both with this specific case, and as a policy for the entire repository?