[Webkit-unassigned] [Bug 156147] [JSC] implement async functions proposal

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 8 15:30:03 PDT 2016


--- Comment #43 from Geoffrey Garen <ggaren at apple.com> ---
> > I believe we create a new Parser for each parsing operation. I would assign
> > flags to the Parser from the global object at Parser creation time.
> I've been looking at doing this --- there are some unfortunate side affects
> (growing the size of every UnlinkedFunctionExecutable, for one).
> Is there any good reason not to just use JSC_OPTIONS for this? This would
> make it easy to enable during tests, without growing a bunch of classes

It would be nice to standardize on RuntimeFlags as the single place where we enable or disable features at runtime.

Why does propagating a runtime flag from global object to parser require adding data to UnlinkedFunctionExecutable, and why does using a JSC::Option avoid doing so?

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160408/d3b03347/attachment.html>

More information about the webkit-unassigned mailing list