Tim Whiting

This is fixed in the latest release, thanks for the feedback!

I seem to recall that this might have been fixed recently?

With the latest koka you can do the following: ```koka effect env val mode: string fun count(items: list): int items.length fun perform(task: a, ?count: a -> int, ?show: a ->...

@BrendanMesters I just checked out that commit, and on the latest release of Koka I was not able to reproduce the error. @jmanuel1 have you seen this or been able...

The example does not actually use non-linear control, so in this case I would hope that Koka compiles it directly to a linear handler even though it is marked ctl....

 I don't know if you knew this, but you can keep the effect definition functions as `ctl` and use the more restrictive `fun` when writing the handler functions for...

I will note that you do need to increase the stack space using ulimit. Maybe it is something that Koka could better document and warn users about. And maybe figure...

Here are the necessary changes to your handlers from the gist: ```koka val reverse = handler { fun ap0(n) -> { Prop(op0(n), ref(c(0.0))) } // No changes to the other...

I'm curious how the equivalent frank program performs on the same machine. Would be interesting comparison to see.

Sorry for the major refactor / splitting of the core that made this PR rather out of date with conflicts. Would you like to update the PR, or would you...