Steve Fink wrote:
It tickles my innate premature optimization kneejerk
reaction, though.
I know this was in context of "fair enough" and "I think you're right",
but I LOL'ed here -- c'mon, C Python! It is way underoptimized compared
to JS VMs.
BTW destructuring plus array return should be optimized to erase the
allocation and use the stack instead. E.g.,
function pair(a, b) { return [a, b]; }
let [x, y] = pair(z, w);
should not allocate a fresh array in pair. Anyone know whether there's a
bug asking for this?
/be
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
