Francis McCabe
Francis McCabe
I will take a look at this. I thought it was done but something 'went wrong' with git when I merged upstream.
I am now crafting an appropriate algorithm.
wasm-unsafe-eval shipped in chrome 97. What additional information are you looking for?
It has not been standardized yet. You need to look at https://github.com/WebAssembly/content-security-policy for the CSP stuff, and https://github.com/WebAssembly/content-security-policy/tree/main/document/web-api and https://github.com/WebAssembly/content-security-policy/pull/40 in particular. (The latter represents unfinished business at the moment)
A combination of factors: 1. It is currently in stage 3 of the process (the standards process is different for wasm & CSP) 2. In order to get to stage...
wasm-unsafe-eval?
You can see a draft of the wasm proposal at https://webassembly.github.io/content-security-policy/
Your assumption is not correct. There are some details still to be worked out; however, the main point is that the interface types' 'version' of a function is conceptually separate...
In all cases, it uses existing mechanisms, specifically, invoking an imported function. There is no separate mechanism for calling adapter functions. Please do not rely on any currently experimental implementations.
An import adapter function has a core wasm signature. Its role is to act as the importee: i.e., when a core wasm module imports a function, the import adapter counts...