3 ms·
Could it be that the vector is hoisted outside of the function's inner scope, promoted to a literal-like datum attached to the outer function? It's obvious fro
by kazinator 2y ago
Could it be that the vector is hoisted outside of the function's inner scope, promoted to a literal-like datum attached to the outer function?
It's obvious from the function that the ArrayBuffer object never escapes from the scope, and is never modified.
If the object is never modified, there is no need to keep newly instantiating it; it can be hoisted to the function and attached to it somehow, so then to get rid of it, we have to lose the function itself.