Say we have a scene with multiple shadow casting lights. These will then generate multiple shadow map textures. Let's say these are passed in as (SPIR-V) bindings 4, 5, 6, 7. The QRhiShaderResourceBinding list is sorted based on the binding so the order is fine in this respect.

However, with Metal (and not with any other backend) we have the concept of native texture (and sampler) binding numbers. Instead of the QRhiShaderResourceBinding's binding number, it is the native binding number that is used when feeding into QRhiBatchedBindings.

Now, if these native bindings happen to be unsorted (so e.g. the native texture binding for SPIR-V binding 7 is smaller than <native binding point for SPIR-V binding 6>), an assert will occur.