On Thu, May 14, 2015 at 11:22 PM, Gijs Kruitbosch <[email protected]> wrote:
> My point is there will be just as many "unexpected" issues when you use > "===" on opaque variables, because you didn't expect that that code in that > other file set this thing to null instead of deleting the property (causing > it to not be === undefined in your comparison) -- for example. This. From the perspective of a library method validating inputs, I've always found it pays off to rely on Postel's principle. Panos _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
