|
|
|
|
|
|
by EGreg
16 days ago
|
|
|
Actually, it's not async programming. It's only async programming the way JS does it... which is unwinding the entire stack, and then starting another stack on the next tick. Instead, many languages have fibers / coroutines / etc. which simply start new stacks elsewhere, and capture the context. |
|
|