Permalink
Reply
On Tuesday, 5 July 2022 at 17:56:05 UTC, Petar Kirov [ZombineDev] wrote:
>auto img = createImage(device, VkImageCreateInfo {
imageType: VkImageType.VK_IMAGE_TYPE_2D,
format: VkFormat.VK_FORMAT_R8G8B8A8_UNORM,
extent: image.size,
mipLevels: image.mipLevels,
arrayLayers: image.layers,
samples: VkSampleCountFlagBits.VK_SAMPLE_COUNT_1_BIT,
tiling: VkImageTiling.VK_IMAGE_TILING_LINEAR, //VK_IMAGE_TILING_OPTIMAL,
usage: VkImageUsageFlagBits.VK_IMAGE_USAGE_TRANSFER_SRC_BIT | VkImageUsageFlagBits.VK_IMAGE_USAGE_SAMPLED_BIT,
sharingMode: VkSharingMode.VK_SHARING_MODE_EXCLUSIVE,
initialLayout: VkImageLayout.VK_IMAGE_LAYOUT_PREINITIALIZED,
});
Looks like this code would benefit more from inferring enum member types (as in the recent DIPX thread). Also it would be great to have struct literals with named fields as the issue requests. Although having to write the struct name is sometimes useful for those reading the code later.
