Add additional type conversion operators to the struct classes to make it easier to interoperate with the Vulkan C API #2087
+11,590
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This improves compatibility with the Vulkan C API so applications can easily use the vulkan_structs.hpp classes with the C API seamlessly.
|
Yes, having both, pointer cast operators as well as reference cast operators (const and non-const) seems to be reasonable. Thanks a lot for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These new operators allow the Vulkan-Hpp struct classes to be more easily used directly with the Vulkan C API.
For example, instead of this:
vk::BufferCreateInfo bufferInfo { .size{sizeof vertexData}, .usage{vk::BufferUsageFlagBits::eVertexBuffer} }; vmaCreateBuffer(allocator, &static_cast<VkBufferCreateInfo const &>(bufferInfo), &bufferAllocationInfo, &vertexBuffer, &vertexBufferAllocation, nullptr);Apps can do this:
vk::BufferCreateInfo bufferInfo { .size{sizeof vertexData}, .usage{vk::BufferUsageFlagBits::eVertexBuffer} }; vmaCreateBuffer(allocator, bufferInfo, &bufferAllocationInfo, &vertexBuffer, &vertexBufferAllocation, nullptr);