You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 1.3.224 and older SDK returns a std::vector<VkImage>.
6fe966c changes this to return a std::vector<vk::Image>. While vk::Image is directly convertible to VkImage, vector<vk::Image> and vector<VkImage> are not directly convertible.
As a result, existing code which assigns the value of getImages() to a variable of type vector<VkImage> will no longer compile with the .229 SDK, and changing the type will make it require .229 and not compile with .224 or older. This doesn't seem like the kind of API change that should have been made in a minor version.
I'm not sure what the best course of action is now that there's been an official SDK release containing this change, but I wanted to get it out there.
The text was updated successfully, but these errors were encountered:
The 1.3.224 and older SDK returns a
std::vector<VkImage>
.6fe966c changes this to return a
std::vector<vk::Image>
. While vk::Image is directly convertible to VkImage,vector<vk::Image>
andvector<VkImage>
are not directly convertible.As a result, existing code which assigns the value of
getImages()
to a variable of typevector<VkImage>
will no longer compile with the .229 SDK, and changing the type will make it require .229 and not compile with .224 or older. This doesn't seem like the kind of API change that should have been made in a minor version.I'm not sure what the best course of action is now that there's been an official SDK release containing this change, but I wanted to get it out there.
The text was updated successfully, but these errors were encountered: