We settled the caching of the template pattern object today. The frozen array is cached based on the global and the strings building up the literal. That means that two literals in different location but exactly the same value, in the same global, will share the frozen object.
On Thu, Nov 13, 2014 at 10:05 AM, Erik Arvidsson <a...@google.com> wrote: > FWIW, IE11 developer preview does cache the call site object. It seems to > do so based on location in the source. Two identical call sites leads to > two objects. Two evals leads to same call site object. > > On Fri, Nov 7, 2014 at 11:51 AM, 'Andreas Rossberg' via v8-users < > v8-users@googlegroups.com> wrote: > >> It is fine to move ahead as far as possible anyway, and implement >> caching once the spec is resolved. We don't plan to stage or ship >> before that, obviously. >> >> /Andreas >> >> -- >> -- >> v8-users mailing list >> v8-users@googlegroups.com >> http://groups.google.com/group/v8-users >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to v8-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > erik > > > -- erik -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
