Is it alive?

[xlab]

[jclc]

Hi, I've been busy lately so I haven't had time to work on this, but I've been doing Vulkan stuff again for the past few days. I'm making my own Vulkan application while learning the API and memory allocation is starting to get relevant for me. It's funny you posted this just now since I was looking at the new version of the VMA library yesterday.

If I recall correctly the issues I had with this were related to c-for-go (xlab/c-for-go#49). I might just make the bindings manually, the API for this doesn't seem that big.

I made the original issue before Go modules were a thing so I hope vulkan-go/vma can depend on vulkan-go/vulkan without any issues.

[xlab]

Yeah, small API surface better be covered manually :)

[jclc]

@xlab How can I get the C struct of a vulkan-go struct type? For example, function vmaCreateBuffer requires a *VkBufferCreateInfo. Doesn't vulkan-go allocate new structs to use with the C functions from the ones it provides in Go?

[xlab]

@jclc you can use Ref() and PassRef()