Using == instead of ===

[yandex]

Using == instead of ===

[ikokostya]

all arguments MUST be explicitly cast

Operator == introduces implicit casts.

[twirl]

Follow the logic:
(a) all parameters must be explicitly cast before being used in any conditions;
(b) so there must be no difference whether you use == or === in conditions, since casting is already done;
(c) why using one more = sign?

[dmikis]

You guys have core disagreement here: we never cast function arguments to types declared in documentation. We may normalise the arguments (i.e., remove optionals or assign defaults to them). Other than that we rely on user follows described function contract.

Yes, it may be bad for APIs such as Maps API, but it works pretty well for us.

[twirl]

You are saying that you don't use polymorphic functions. Either state this in a codestyle or provide guidance what to do in such case. Personally, I simply don't understand then why using === at all if you know all types at runtime (with possible exclusion for null, since it's an object — known language bug)/

[vtambourine]

(c) why using one more = sign?

To avoid possible error and misuse.