How does Chrome's garbage collector handle async functions that never return a value?

Does this cause any issues? I’d guess not, as long as we don’t attempt to await an async function without a return value?

I’ve been looking for information on this, and I’m sure it’s out there (maybe even obvious) but I haven’t had any luck finding a definitive answer.

162 thoughts on “How does Chrome's garbage collector handle async functions that never return a value?”

  1. Magnificent goods from you, man. I have understand your stuff previous to and you are
    just too fantastic. I actually like what you have acquired here, certainly
    like what you’re saying and the way in which you say it.

    You make it entertaining and you still take care of to
    keep it wise. I can not wait to read much more from you.

    This is actually a wonderful website. http://droga5.net/

    Reply