simon place

i imagined there was some 'state' that was unanticipated, but when fixed, unfortunately, any info about the 'state' was probably lost. hence this report, to be found if happens again...

for type info use "go doc", see; https://pkg.go.dev/cmd/go#hdr-Show_documentation_for_package_or_symbol and for vilkan-go examples; https://github.com/vulkan-go/demos

``` > go doc PhysicalDeviceIDProperties package vulkan type PhysicalDeviceIDProperties struct { SType StructureType PNext unsafe.Pointer DeviceUUID [16]byte DriverUUID [16]byte DeviceLUID [8]byte DeviceNodeMask uint32 DeviceLUIDValid Bool32 // Has unexported fields. }...

also just look at the packages online doc, which was generated by go doc. https://pkg.go.dev/github.com/vulkan-go/vulkan#PhysicalDeviceIDProperties

OK, this package calls into vulkan, which is compiled c, the unsafe pointer is 'unsafe' due to this, the demos show you this working. you call funcs to get unsafe...

> In playground instead of a zip file: https://go.dev/play/p/MwWuoC7fDFg?v=gotip neat (inlining files)

same only without import (works as)... [play.ground/foo](https://go.dev/play/p/GBd0x8WqlDh?v=gotip)