The Ash builder methods are now used instead of raw pointers, so that lifetimes are correctly tracked. This did, however, need some significant refactoring because of how borrowing rules work. For that reason, I moved all Ash struct construction into the structs themselves (as methods). The methods and structs follow a tiered logic where each value borrows from those below it:
The Ash builder methods are now used instead of raw pointers, so that lifetimes are correctly tracked. This did, however, need some significant refactoring because of how borrowing rules work. For that reason, I moved all Ash struct construction into the structs themselves (as methods). The methods and structs follow a tiered logic where each value borrows from those below it:
to_vk->ash::vk::FooCreateInfoto_vk_extensions->mut FooCreateInfoExtensionsVkto_vk_fields1->FooCreateInfoFields1Vkto_vk_fields1_extensions->mut FooCreateInfoFields1ExtensionsVkto_vk_fields2->FooCreateInfoFields2Vkto_vk_fields2_extensions->mut FooCreateInfoFields2ExtensionsVkto_vk_fields3->FooCreateInfoFields3VkMutable borrows are needed for the extension structs because
push_nexttakes a mutable reference.The
DeviceFeaturesandDevicePropertiesconstruction have been left out of this, those need more attention that will be done in a separate PR.