This is to benefit from the uncurried calls in JS.
After a very simple profiling of our purple rain demo, I've noticed that if we made just the get/set functions not go through Curry._3, we'd more than half the runtime of the user code, going from 19ms to 8ms, in our purple rain demo.
Funnily enough it doesn't really change the frame rate, because it seems like the operations we're doing on the GPU block the call to requestAnimationFrame:
This is to benefit from the uncurried calls in JS. After a very simple profiling of our purple rain demo, I've noticed that if we made just the get/set functions not go through
Curry._3, we'd more than half the runtime of the user code, going from 19ms to 8ms, in our purple rain demo.Funnily enough it doesn't really change the frame rate, because it seems like the operations we're doing on the GPU block the call to requestAnimationFrame: