Closed hikari-no-yume closed 9 years ago
In Chromium 43 I don't get a TypeError
but instead the bound action is performed immediately on page load, which is arguably even worse. It seems that the Closure compiler is optimizing away the unused RealWorld#
argument that IO computations carry, which causes trouble when the eval/apply machinery tries to use arity info in function applications.
I'm not entirely convinced that Closure should really be doing that, but I'll look into a workaround.
Posted related issue to closure-compiler: https://github.com/google/closure-compiler/issues/1046
Ah, I should've mentioned I was using Fx, that's where I was getting this behaviour. Odd that the two JS engines would behave differently here.
Patching Closure to not mangle Function.length
turned out to be the simplest option. Running haste-boot --force --no-libs
should fetch the new Closure binary without forcing a rebuild of any libraries.