Commits on Nov 22, 2022

1. Call Vec::set_len() after checking for Vulkan errors …

   The entire reason for calling `unsafe` `set_len()` after the Vulkan
   driver function call is to ensure the `Vec` never gives safe access to
   uninitialized values (as allocted via `Vec::with_capacity()`).  This
   contract is broken within the implementation of these functions by
   temporarily setting a nonzero length when the Vulkan driver may not have
   initialized the underlying data at all, and communicated this by
   returning an error code.
   
   Simply check the error code first, before jumping to a now-infallible
   codepath that calls `.set_len()` and always returns `Ok()`.

   

   MarijnS95 committed Nov 22, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for 8f22389
   • Browse repository at this point

   Copy the full SHA

   8f22389 View commit details

   Browse the repository at this point in the history