On Fri Sep 1 10:25:54 2023 +0000, Giovanni Mascellani wrote:
A workaround to parse INF is to enter a very large number. I think some test has `1e99` or so.
Though it turns out that it's just better to avoid it: on WARP I get this: ``` shader_runner:648: Section [test], line 70: Test failed: Got {0.00000000e+000, 1.00000000e+003, 1.11848115e+009, -1.00000000e+003}, expected {0.00000000e+000, 1.00000000e+003, 1.#INF0000e+000, -1.00000000e+003} at (0, 0). ```