Hey Ben, Mainly that the generator state is saved/restored by just copying the full function frame in fullcodegen, which is of course not portable to the optimizing compilers. :-) A better approach would basically context allocate everything and just reenter the context, but that will be slow by default in the interpreter/fullcodegen; so we need to find a compromise in between.
HTH, Benedikt On Thu, Dec 17, 2015 at 11:13 AM, Ben Noordhuis <[email protected]> wrote: > On Thu, Dec 17, 2015 at 4:18 AM, Benedikt Meurer <[email protected]> > wrote: > > Hello Donato, > > > > Currently generators cannot be optimized due to certain implementation > > choices. But we plan to revisit those decisions next year, which should > > allow us to optimize generator functions as well. > > > > HTH, > > Benedikt > > Benedikt, for my edification: what implementation choices are those? > > (For background, I'm working on a toy JS run-time and I hope to get > around to implementing generators in the next few weeks.) > > -- > -- > v8-users mailing list > [email protected] > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
