Tim Whiting
Ahh, you are right, this isn't a problem with methods, so its a bad interaction between library based privacy and class implementation.
Yeah, this has never worked. I'll look into it
Koka's compiler provides a Haskell library without the main, so it definitely can be reused without necessarily modifying the compiler directly, though of course you could maintain a fork. The...
Yes, likely. You might be able to get away with writing Koka's Core Syntax directly which has it's own format and can be parsed: https://github.com/koka-lang/koka/blob/dev/src/Core/Parse.hs. However, it might need some...
Actually, I just realized we already have the `any` type which is a boxed value. I would add the following to a "core" module that you always import. ```koka extern...
Sorry about this, handlers do build up on resumption, and this is known: https://github.com/koka-lang/koka/blob/39b4bec7327dbbcb2f83ce7aca5fe061931a4dc3/lib/std/core/hnd.kk#L410. `list/map` should be tail-recursive, and optimized, I'd have to see the generated code though to see...
I guess even though `map` is tail recursive your `recurse` is not. So that is likely part of the issue. In the meantime there are tricks to make something like...
Just took a closer look, and actually ran it. This has nothing to do with handlers, or stackoverflow in browsers. It has more to do with overwhelming the console tracing...
That's fine, we can leave this open as a general issue for stack overflow detection. (Which is not handled in C either). Is the original issue something that hit this...
I'm glad you were able to find a workaround for now.