26 Nov
2024
26 Nov
'24
4:07 p.m.
This looks improved, but I’m not sure why the `parent` needs to be part of `vulkan_object`, or why its declaration is hidden behind a macro. Couldn’t it simply be a pointer in the type-specific structs instead?
Sure, I'll leave it separate then. It was making things slightly more convenient by factoring the object declarations and their initialization in vulkan_object_init. But not all objects need to keep track of their parents, so probably more flexible to keep them separate. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/6427#note_88941