chtenb

To be honest, I didn't figure out from the error message it was the parameter name that was the problem, until I trimmed it al the way down to this...

The rules about shadowing make sense to me in isolation. But the combination with existing naming conventions makes it akward in some cases. 1. In larger functions, using single-letter variable...

That's fair. The following works fine and is readable too ```koka ref struct model value : int fun bool/model(b : bool) : model Model(if b then 1 else 0) fun...

Ah, I had completely overlooked that detail (the `.. = name` part) when reading it. Interesting, that does cover a lot of basic usecases of factory functions indeed.

No, unfortunately I have very little experience in using Haskell beyond small toy projects. But I have heard many times people complaining about these bugs being hard to track down....

Over at https://github.com/helix-editor/helix/pull/8727/files @mtoohey31 noticed that the `mod` keyword isn't found on the dev or master branches. Where does this keyword come from?

I found a reasonably small repro: ``` import std/text/parse pub fun main() println("start") val input = join(list(0, 999).map(fn(n) "aaaaaaaaa" ++ show(n)), "\n") println("parsing " ++ input) val x = parse(slice(input))...

Indeed, the following makes the reproduction exit correctly: ``` editbin.exe .koka\v2.4.2\clang-cl-debug\repro.exe /STACK:100000000 ``` Thanks for the hint

I'm not sure I follow. The main() function has access to the console effect. If I comment the take-exn call instead, and leave the println uncommented it works.

I'm running into the same or very similar issue. In my case it doesn't matter if I use unsafe-no-div or unsafe-total, both will crash. Here is an example. We define...