In KhronosGroup/Vulkan-Hpp#2443, we have moved off the include-everything-then-using style, which led to a lot of edge cases and hardcoding to the so-called ABI-breaking style.
This requires some additional work, but the upshot is that the same code path is used in the generator, without having to additionally cache things and print out thousands of using statements, making the module interface itself much shorter, leading to reduced maintainer workload as well.
Could this be considered for VMA-Hpp?
Also CCing @M2-TE who helped a lot there.
In KhronosGroup/Vulkan-Hpp#2443, we have moved off the include-everything-then-using style, which led to a lot of edge cases and hardcoding to the so-called ABI-breaking style.
This requires some additional work, but the upshot is that the same code path is used in the generator, without having to additionally cache things and print out thousands of
usingstatements, making the module interface itself much shorter, leading to reduced maintainer workload as well.Could this be considered for VMA-Hpp?
Also CCing @M2-TE who helped a lot there.