You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The name of the function is not important at any of the call sites since
we only use this helper to modify JS library functions, and JS library
functions get their name set explicitly at the top of
`processLibraryFunction`.
Also, rename the function just in case there are external caller of this
function, this will make it clear they need to update their code.
This change was motivated by #19539 where it helps to avoid worrying
about functions names.
assert(!ENVIRONMENT_IS_WASM_WORKER, "Attempted to call proxied function '${name}' in a Wasm Worker, but in Wasm Worker enabled builds, proxied function architecture is not available!");
198
+
snippet=modifyJSFunction(snippet,(args,body)=>`
199
+
function(${args}) {
200
+
assert(!ENVIRONMENT_IS_WASM_WORKER, "Attempted to call proxied function '${mangled}' in a Wasm Worker, but in Wasm Worker enabled builds, proxied function architecture is not available!");
0 commit comments