Le 29/03/2014 20:16, Till Schneidereit a écrit :
On Sat, Mar 29, 2014 at 3:05 PM, Chris Peterson <cpeter...@mozilla.com>wrote:
On 3/29/14, 11:38 AM, Till Schneidereit wrote:
Just stumbled upon this:
https://groups.google.com/forum/#!topic/mozilla.dev.gaia/Il3DiRpIZ0U
In this particular case, the right conclusions was arrived at, but I
wonder
if we should try to be more proactive about getting people to not use any
features we want to remove eventually. Or, at least, be free to deoptimize
as needed.
Till, by "be more proactive", do you just telling people (on the lists you
mentioned) or adding warnings (to jshint or console)?
At the JS work week, we discussed adding telemetry for JS 1.8 (and other
non-standard <script> type values). Is that still interesting?
We should do all three, I think. I filed bug 988386[1] on the last. Note
that that's for web content, though, not platform/Firefox/Gaja code.
nor addons?
The second is the most difficult to get right, though: we don't want warning
fatigue to completely undermine any effect.
At the same time, platform/Gaia folks are easier to reach out and
"anyone" can write a patch to fix the issue (unlike web content). The
addon part is a bit fuzzier.
It's interesting to see that changes to generators didn't seem to break
too many addons [1].
Happy to write doc on transitioning from a SpiderMonkey-specific feature
to an ES6 one if that can help make the warning message more efficient
(with a link to the doc on how to transition).
David
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=907077#c86
_______________________________________________
dev-tech-js-engine-internals mailing list
dev-tech-js-engine-internals@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
