Add notes about where we'd need to handle queue resource sharing

* This won't be handled until after 1.0 (since that's when we'll support multiple queue families, etc.
2026-05-12 21:10:42 +00:00 · 2015-12-02 20:45:36 +01:00
parent acb38757cd
commit 3c8fe0e44a
4 changed files with 7 additions and 1 deletions
@@ -44,6 +44,7 @@ In no particular order, features that are not planned until after 1.0.
 * Stepping inside vkCmdExecuteCommands
 * Support for replaying captures on a different machine to where they were captured
 * Shader debugging
+* Sharing resources between different queues, and ownership changing hands
 * Mesh output data after geometry and tessellation shaders
 * Vertex picking
 * Pixel history