On Aug 22, 2012, at 1:39 PM, chromatic wrote: >> And I would prefer the fatality over an easily-missed ambiguity warning. I >> want to know when it's doing something ambiguous ASAP, so I can fix it and >> move on. The fix will always be simple. > > You *can* make this warning fatal in your own code. Going the other direction > is more difficult. Maybe it could be fatal under `use strict` then? DavidThread Previous | Thread Next