tree d8bc72f677d5ffef59496ca7fe1170c0b88776a5
parent dec7f7d6578e87cbad1fcc436646fb7834126d9e
author Ingvar Stepanyan <me@rreverser.com> 1694478408 +0100
committer Ingvar Stepanyan <me@rreverser.com> 1694478408 +0100

Don't mark proxy async funcs as Asyncify

In #19093 both async functions and functions marked with `NAME__async: true` were marked as functions to be processed by Asyncify.

However, looking at usages, standalone async functions are currently used with emscripten_proxy_finish-based callbacks and not with Asyncify.

Besides, such functions can't work with Asyncify unless we add automatic `Asyncify.handleAsync` wrapping around each such function as well. We could do that, but given that there are already is some confusion around what async means for any particular function, it seems better to keep explicit calls to `emscripten_proxy_finish` and `Asyncify.handleAsync` correspondingly.

Hence, in this PR I'm not adding more automatic wrapping but instead just removing the assumption for standalone async functions which should somewhat reduce code size as they will no longer be Asyncify-ed when not necessary.