disallow ImageRead, ImageWrite, ImageFetch with ConstOffset
dneto0 opened this issue · 1 comments
dneto0 commented
In WGSL, textureLoad, textureStore do not have overloads with an offset parameter.
See also https://bugs.chromium.org/p/tint/issues/detail?id=408
dneto0 commented
Vulkan permits use of ConstOffset with ImageFetch.
I suspect there is a missing rule to ban ConstOffset with ImageRead, ImageWrite.