On Wed Mar 13 16:06:44 2024 +0000, Rémi Bernon wrote:
The rationale was that we cannot map callbacks during creation, so this would be unbalanced with callbacks during destruction (if anything tracks leaks for instance), and we will need instead to generate our own callbacks to balance it. Still I'm also fine keeping it unbalanced, though I think it wasn't completely consistent.
I think that this being unbalanced matches how it looks from host Vulkan point of view: constructors can't expect the caller to understand the new handle in callbacks (so presumably they won't emit such callbacks), while destructors can.