If the arguments are not of the same type, then an appropriate type coercion is done for them before comparison.

JavaScript has the same semantics for , referred to as "equality without type coercion".

Many languages provide type transfer functions so that the programmer can control where and when the type coercion is performed.

Thus, when multiple subtyping relationships are defined, one must be careful to guarantee that all type coercions are coherent.

It gets used in certain (rather rare) circumstances, e.g. as.vector(x, "any"), indicating that type coercion should not be done.

In the case of stone lion, a conflict of central attributes will be detected, fulfilling the requirements for a negating type coercion.

In the second and third cases, floating-point addition must be invoked (with type promotion, or type coercion, in the third case).

Automatic type coercion by the equality comparison operators ( and ) can be avoided by using the type checked comparison operators, ( and ).

Coercion functions for records and disjoint union subtypes may be defined componentwise; in the case of width-extended records, type coercion simply discards any components which are not defined in the supertype.

Algol 68's many little-used language features (for example, concurrent and parallel blocks) and its complex system of syntactic shortcuts and automatic type coercions made it unpopular with implementers and gained it a reputation of being difficult.

The inline function allows the compiler to check/coerce parameter types-in this particular example this appears to be a disadvantage, since the 'max' function as shown works equally well with different parameter types, but in general having the type coercion is often an advantage.

Automatic type coercion by the comparison operators may differ for cases of mixed Boolean and number-compatible operands (including strings that can be evaluated as a number, or objects that can be evaluated as such a string), because the Boolean operand will be compared as a numeric value.