deno
deno copied to clipboard
refactor(core): remove opAsync
How was the "jitting" for the async functions done again? Did it rely on new Function usage?
How was the "jitting" for the async functions done again? Did it rely on
new Functionusage?
It's done in 01_core.js in initializeAsyncOps and yes, it uses new Function, but that's problematic as described in https://github.com/denoland/deno/issues/16535 and Divy will rework it to do it from Rust side.
@littledivy is anything blocking this PR?
Please wait for https://github.com/denoland/deno/pull/17648 to land before merging this PR.
Fun rebase in store.
Uno reverse by https://github.com/denoland/deno/pull/17899

opAsync will stay.