![]() |
|
The Truth About Cancelling Async/Await: Youre Mostly Just Ignoring Results - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45) +--- Forum: Grayhat • Purple Team • Hybrid Security (https://hackforums.net/forumdisplay.php?fid=449) +---- Forum: Beginner Hacking (https://hackforums.net/forumdisplay.php?fid=4) +---- Thread: The Truth About Cancelling Async/Await: Youre Mostly Just Ignoring Results (/showthread.php?tid=6316491) |
The Truth About Cancelling Async/Await: Youre Mostly Just Ignoring Results - Stanley - Dec 24, 2025 The Truth About “Cancelling” Async/Await: You’re Mostly Just Ignoring Results JavaScript can’t truly cancel async/await work—most “cancellation” just stops waiting. https://hackernoon.com/the-truth-about-cancelling-asyncawait-youre-mostly-just-ignoring-results?source=rss RE: The Truth About Cancelling Async/Await: Youre Mostly Just Ignoring Results - Terry A. Davis - Dec 24, 2025 I think aside from design choices of any such feature like instant cancel, imaging the over head on a server that anytime before it continues the operation (thinking CPU scheduler here), that it has to check cancellation tokens and other factors, THEN! Go back to it, seems like you'd be spending time you be like wait hold on let me check, wait sorry I was told to cancel that check so ignore that, ok now I'll res- oh I can stop now. |