Make GenericMemoryAllocatorCreateInfo::block_sizes
more flexible
#2319
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.
Changelog:
There wasn't really any reason block sizes would have to be restricted to the level of heaps. Apart from the added flexibility this also makes the code cleaner. I also merged the two lifetimes
GenericMemoryAllocatorCreateInfo
into one as I don't think it's needed, and replaced the use ofash::vk::MemoryPropertyFlags
with our own. This was originally the ash type because before #2073, theArrayVec
would have taken up a huge amount of space, and would need a costly conversion to the bitfield anyway.