How heavily does this rely on CGO/C++ bindings?

[ghost]

Just curious, how close to being pure Go is this project? I see some C files in the repo here but I thought I should ask the devs rather than guess...

[xlab]

@rucuriousyet there are the official C API header files from Khronus
https://github.com/vulkan-go/vulkan/tree/master/vulkan

The bindings are generated for them. Vulkan architecture works that way — you have an API to call functions from a shared library, which is a single entrypoint and acts like a facade. I'm talking about libvulkan.so

It's possible to generate Go code from XML spec and call functions from libvulkan without CGo, but Vulkan works with C memory layout, so you will still be responsible for layouts and alignment. Better to hand that to CGo.