Vulkan module fails to compile

[oatmealine]

Hi - I'm not sure if this repository is abandoned or not, but it seems that since the last commit the Vulkan support in vk.cpp has stopped working. As of the most recent Vulkan version, it outputs a bunch of errors about invalid types, not finding names, etc.:

vk.cpp:21:28: error: 'VkLayerInstanceDispatchTable' was not declared in this scope
   21 |  std::unordered_map<void*, VkLayerInstanceDispatchTable> instance_dispatch_;
      |                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vk.cpp:21:56: error: template argument 2 is invalid
   21 |  std::unordered_map<void*, VkLayerInstanceDispatchTable> instance_dispatch_;
      |                                                        ^
vk.cpp:21:56: error: template argument 5 is invalid
vk.cpp:22:28: error: 'VkLayerDispatchTable' was not declared in this scope
   22 |  std::unordered_map<void*, VkLayerDispatchTable> device_dispatch_;
      |                            ^~~~~~~~~~~~~~~~~~~~
vk.cpp:22:48: error: template argument 2 is invalid
   22 |  std::unordered_map<void*, VkLayerDispatchTable> device_dispatch_;
      |                                                ^
vk.cpp:22:48: error: template argument 5 is invalid
vk.cpp: In function 'VkResult deshade_vkCreateInstance(const VkInstanceCreateInfo*, const VkAllocationCallbacks*, VkInstance_T**)':
vk.cpp:181:2: error: 'VkLayerInstanceDispatchTable' was not declared in this scope
  181 |  VkLayerInstanceDispatchTable dispatch_table;
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vk.cpp:183:2: error: 'dispatch_table' was not declared in this scope
  183 |  dispatch_table.GetInstanceProcAddr = (PFN_vkGetInstanceProcAddr)
      |  ^~~~~~~~~~~~~~
vk.cpp:195:30: error: request for member 'insert' in 'context.ContextVK::instance_dispatch_', which is of non-class type 'int'
  195 |   context.instance_dispatch_.insert({ DispatchKey(*pInstance), dispatch_table });
      |                              ^~~~~~
vk.cpp: In function 'void deshade_vkDestroyInstance(VkInstance, const VkAllocationCallbacks*)':
...

Is there any chance this could be fixed? I find this to be a really interesting tool and I don't want to see it get abandoned for the rest of time. Thanks!