Primary thing to pay attention to is the new ConstantOrOverrideValueChecker utility class (rolls off the tongue, huh?) This is performing the same quantization step as before but now has the opportunity to force a subcase to be skipped if the checked value is found to be in a range where the overflow rounding behavior is ambiguous.
If we think this is a good direction then I'll go back and update a bunch of the tests I've already completed to use the new utility class for consistency/completeness.
Requirements for PR author:
[x] All missing test coverage is tracked with "TODO" or .unimplemented().
[x] New helpers are /** documented */ and new helper files are found in helper_index.txt.
[x] Test behaves as expected in a WebGPU implementation. (If not passing, explain above.)
[x] Test have be tested with compatibility mode validation enabled and behave as expected. (If not passing, explain above.)
Fixes #3623
Primary thing to pay attention to is the new
ConstantOrOverrideValueChecker
utility class (rolls off the tongue, huh?) This is performing the same quantization step as before but now has the opportunity to force a subcase to be skipped if the checked value is found to be in a range where the overflow rounding behavior is ambiguous.If we think this is a good direction then I'll go back and update a bunch of the tests I've already completed to use the new utility class for consistency/completeness.
Requirements for PR author:
.unimplemented()
./** documented */
and new helper files are found inhelper_index.txt
.Requirements for reviewer sign-off:
When landing this PR, be sure to make any necessary issue status updates.