The bug is surprising, in that it claims that the bytecode that consumes the value determines whether a warning is issued (SETLOCAL;CALL), rather than the bytecode doing the fetch.
Is that the intended behavior? I can't see how that makes much sense. On Dec 19, 2014 2:55 PM, "David Rajchenbach-Teller" <dtel...@mozilla.com> wrote: > I am going to suggest, once again, that warnings generally noise and > should be replaced by actionable errors, at least when the code is > executed in a test suite. > > See > https://groups.google.com/forum/#!topic/mozilla.dev.platform/gqSIOc5b-BI > > Cheers, > David > > On 19/12/14 21:19, Jason Orendorff wrote: > > So if you go to about:config and set the javascript.options.strict pref, > > you'll get warnings about accessing undefined properties. > > > > js> Math.TAU > > undefined > > /!\ ReferenceError: reference to undefined property Math.TAU > > > > (It says "ReferenceError", but your code still runs normally; it really > is > > just a warning.) > > > > Is anyone using this? Bug 1113380 points out that the rules about what > kind > > of code can cause a warning are a little weird (on purpose, I think). > Maybe > > it's time to retire this feature. > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1113380 > > > > Please speak up now, if you're still using it! > > > > -j > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > > > -- > David Rajchenbach-Teller, PhD > Performance Team, Mozilla > > > _______________________________________________ > 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
