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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=156147

--- Comment #22 from Caitlin Potter (:caitp) <caitp at igalia.com> ---
(In reply to comment #21)
> Because this is a bleeding-edge language feature, I think we need a runtime
> flag to enable / disable it. For example, we will probably disable it in the
> Safari Technology Preview until it's more mature.
> 
> It's OK if the flag doesn't cause all the code to be compiled out. The goal
> is just to avoid exposing a language feature to the web before it's mature.
> 
> (There was some discussion on webkit-dev recently about runtime flags for
> new features. I think what I"m saying here is consistent with that
> discussion.)

I agree whole-heartedly that a flag would be beneficial :) What I meant was, currently there's no apparent mechanism for attaching the RuntimeFlags class to the Parser (or the VM object, somewhat surprisingly). So, it looks like it would be a quicker fix to add a compile-time flag.

The mechanism for adding runtime flags to the parser is a bit important, for example if multiple tests are run using the same VM asynchronously, some may depend on different sets of flags (a situation which affects V8's C++ tests). It may be possible to just pass in a flags option, but I'm not sure if the Parser is directly exposed to the API, or what.

Happy to add the flag, could just use a little guidance on an approach that will work well for JSC/WebKit.

-- 
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/20160404/3fe33c58/attachment-0001.html>