I am concerned about the accidental consequences of turning this on for nightly/aurora. What if we start writing browser code that relies on these features which unexpectedly starts failing in beta?
I presume the value of enabling this in nightly/aurora is that we can get web developers to experiment and report bugs? Is that something we can do asking them to explicitly turn this on via pref? Or are you worried about this feature accidentally breaking existing web content and you want to get bug reports from normal users? Could we mitigate risk by disabling this feature in chrome code by default until you're confident in its readiness to ship? --BDS On Mon, Mar 27, 2017 at 10:33 AM, Tooru Fujisawa <arai.un...@gmail.com> wrote: > I just landed the initial implementation of Async Iteration proposal > (async generator and for-await-of syntax), as non-release-only feature. > > https://bugzilla.mozilla.org/show_bug.cgi?id=1331092 > > The implementation is only for the testing purpose (for finding spec bug > etc), and the semantic change in the spec is highly expected. They're not > yet ready for production usage, either in browser code or in testcases. > Please wait for a while :) > > -- > > arai > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
