HN user

jufter

5 karma
Posts0
Comments10
View on HN
No posts found.

..kind of breaks the typical stack-trace patterns.

The expectation that iterative recursion ought to have a call stack is the problem here and wouldn't be up for debate if people had done their due diligence and read their SICP.

how do i know that the CPU thing does not block inside my async io thing?

I think it's common sense to not interweave IO with long-running CPU, hence sans IO.

If you want to go that route, we already have solutions: goroutines and beam processes.