The baking of a pipeline is usually delayed until that pipeline is actually used. If you have a lot of pipelines, and Anvil::GraphicsPipelineManager::bake triggers an assertion failure in one of them, it can be difficult to tell which pipeline actually triggered it. For cases like that it would be handy if a debug name could be assigned to Anvil::BasePipelineInfo objects, similar to how a name can be assigned to resources like Anvil::Image.
The baking of a pipeline is usually delayed until that pipeline is actually used. If you have a lot of pipelines, and Anvil::GraphicsPipelineManager::bake triggers an assertion failure in one of them, it can be difficult to tell which pipeline actually triggered it. For cases like that it would be handy if a debug name could be assigned to Anvil::BasePipelineInfo objects, similar to how a name can be assigned to resources like Anvil::Image.