Open Gurkenglas opened 7 years ago
Yes, indeed. This stack trace pattern looks like something that can be optimized with #442. That should be implemented within the next couple of weeks.
Closing because that issue can solve this. I'll verify that this problem is fixed once I implement #442 and re-open it if it isn't.
The referenced issue is closed, any updates?
This needs to be checked out. We now have a function called trampolineIO :: IO a -> IO a
which avoids stack blowouts. In this case it did not help and we need to look into why.
This ought to take constant space, as it does in Haskell.