Nenad Rakocevic
Nenad Rakocevic
It seems related to `catch` behavior in global context.
Actually, the reported issues above in the global context and in `#system` are not related.
> This doesn't allow me to work on HOFs, as I can't imagine a workaround :( Why would your work need a `catch` in global context instead of having it...
I'm working on fixing the global context case. For the other one, it works as it should. You assume wrongly that `fire` is equivalent to `throw`. `fire` is meant to...
> trim/tail #{000000} > == #{00} ; >> head trim/tail probe at #{11000000} 2 > #{000000} > == #{1100} ;
You're right, I've overlooked it.
Thanks for this PR! I will review it in details and test that new features in the next days.
That behavior has been changed several times. This currently mimics C semantics, where it's user's responsability to handle when/how each locals would be initialized. Making it more strict means that...
Should be possible, I'll look into that.
@greggirwin @endo64 Could we write down the rule with want for `trim` on binaries clearly and make the trivial fix for this ticket?