Re: Notification for new navigation timing entries

Though, now that I really grok what you wrote, Boris, you clearly get what
I'm trying to do and know way more about how to do it than I do! I'm very
open to suggestions and saving-from-myself here. :)

On Thu, Feb 12, 2015 at 2:20 PM, Nat Duca <nduca@google.com> wrote:

> Yeah it seems like we should ditch the typedef rename and introduce a new
> LazyPerformanceEntryArray object.
>
> The design goal I had in mind for this was to avoid construction of
> PerformanceEntry objects until you actually needed them. Accessing these
> entries is quite slow to just buffering them.
>
> That is, it was intentional to not have forEach and other things on these
> arrays. This is like NodeList --- QuerySelectorAll gives back a ton of
> stuff, but you have to work to get the actual contents.
>
> In this case, too, good performance timing discipline requires you to not
> crack open performance events when you get these records.
>
> So basically, I actually think its bad to support forEach on the object
> without some additional work....
>
> We could, perhaps, have a sequence<PerformanceEntry> AsSequence() method
> for people who want to treat this as a seuence?
>