lukechilds/node - node - Gitea: Git with a cup of tea

Tree: aefbd57514

Ryan aefbd57514 Add stack to promise.wait(). The problem was that if promise A was waiting and promise B was created and then also told to wait (from some callback coming off the event loop), and then promise A finished, promise B's wait would return. Promise A's wait would not return until promise B was finished. This is incorrect. To solve this issue properly, one probably needs to allocate separate execution stacks. I use, instead, Poor Man's Coroutines. We continue to use the main execution stack and force promises created most recently to return first. That is even if Promise A finishes first, neither wait() returns. Not until Promise B finishes, will its wait() return. After that is complete, Promise A's wait() will return. This introduces the problem of growing the "wait stack" infinitely. Thus I've added a strong warning to the documentation only to use this operation sparingly. require() and include() seem to be the proper use case for such a thing: they are called usually at program start up - they don't take too long to finish and they won't be called so often. Let's experiment with this stop-gap. If the infinite promise stack becomes a problem for many, then I will remove promise.wait() entirely or perhaps only use it for thread pool events.		15 years ago
..
api.txt	Add stack to promise.wait().	15 years ago
index.html	bump version	15 years ago
pipe.css	Modify website layout.	15 years ago
sh_javascript.min.js	Work on website styling.	16 years ago
sh_main.js	Clean up doc intro and syntax highlighting.	16 years ago
sh_vim-dark.css	More node.http.Client docs	16 years ago
toc.js	Restyle website/api.html. Now looks like the front page.	15 years ago