Ilya Rezvov

No, I'm not familiar with such precedence. Other function objects([AsyncFunction](https://tc39.es/ecma262/#sec-async-function-constructor), [AsyncGeneratorFunction](https://tc39.es/ecma262/#sec-asyncgeneratorfunction-constructor)) behave the same way as their `BoundFunctionObject` in any applications. So there is no such problem with them.

As I understand TC39 `JSFunction` interface could be reference in the same fashion as `ArrayBuffer` interface introduced in the spec. I overlooked this approach initially, but it looks right to...

It is already doable with JS without glue code and in theory could be easily optimized by VMs(by unwrapping `BoundFunctionExoticObject` of import) ```javascript new WebAssembly.Function({parameters:["externref", "externref"]}, Function.prototype.call.bind(Node.prototype.appendChild)); ```

> My understanding is that nothing special ought to happen in that case — the already wrapped inner function is treated as any old JS function. That simply results in...