In some cases, usually when the 0 came first, the existing code for uninoing unsigned ranges would throw away potential 0 results, leading to unwanted constant folding.
()This bug was revealed while investigating correctness issues on my GPU range ID branch.)
In some cases, usually when the 0 came first, the existing code for uninoing unsigned ranges would throw away potential 0 results, leading to unwanted constant folding.
()This bug was revealed while investigating correctness issues on my GPU range ID branch.)