I've noticed that four members of the VkSamplerCreateInfo struct are floats, but assigned integer values in various places. Although implicit type conversion will be performed at compile time, I think this should be changed because of two reasons:
Assigning integer values to the members may lead to the assumption that the members itself are of an integer type. This wrong assumption may lead to trouble (missing casts, invalid bitwise operations).
The member types are an important semantic clue (f.i. one could assume that maxAnisotropy might represent a number of samples, whereas this idea does not seem probable when looking at a float assignment).
The definition of VkSamplerCreateInfo as of Vulkan 1.2 can be found here.
I've noticed that four members of the
VkSamplerCreateInfo
struct are floats, but assigned integer values in various places. Although implicit type conversion will be performed at compile time, I think this should be changed because of two reasons:maxAnisotropy
might represent a number of samples, whereas this idea does not seem probable when looking at a float assignment).The definition of
VkSamplerCreateInfo
as of Vulkan 1.2 can be found here.