Ralithundefined behavior is, by definition, unpredictable
Ralithit can do different things depending on compile mode, target environment, phase of moon, etc
Ralithit's up to you to construct them and pass them in
Ralithotherwise the memory management situation would be a nightmare
ash::vk::extensions::DebugUtils, but it seems that I can't find similar thing for NVIDIA extensions, so right now I don't know how to use those extensions in ash...
vkGetPhysicalDeviceFeaturesI will get a segmentation fault. Not sure if it's a probelm in VulkanSDK for macOS, or a problem in