max_binding inconsistency in vulkan descriptor set drivers
Upon inspection of !9880 (comment 858022), it was noted that use of max_binding
among different drivers were used inconsistently. Some were initialized as uint32_t max_binding = 0
, or int32_t max_binding = pCreateInfo->bindingCount > 0 ? 0 : -1;
.
Based on this variables are initialized questionably.
!9880 (comment 858009) an example of a case.
The intended use of max_binding needs to be understood and implemented consistently across drivers.