at least now we agree object literals *add* overhead and with current JS.next typed structs/arrays proposal you can bet developers will do those kind of non-sense things ;-)
I have updated the test case using a second Int32Array loop simply to access the index On Sun, Sep 18, 2011 at 6:03 AM, Brendan Eich <bren...@mozilla.com> wrote: > On Sep 17, 2011, at 10:34 PM, Andrea Giammarchi wrote: > > > Brendan I wrote I did it on purpose trying to predict what JS devs will > do once JS.next will bring ctypes like syntax. > > My objection is that you're confounding test2 by adding object literal > overhead to each loop iteration, in addition to typed array accesses. You > want to focus on just the typed array accesses, from what I can tell of your > benchmark. > > /be
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
