Implements

Remarks

Notes to Callers

Compiler overload resolution may account for an apparent difference in the behavior of the two Equals(Int32) method overloads. If an implicit conversion between the obj argument and an Int32 is defined and the argument is not typed as an Object, compilers perform an implicit conversion and call the Equals(Int32) method. Otherwise, they call the Equals(Object) method, which always returns false if its obj argument is not an Int32 value. The following example illustrates the difference in behavior between the two method overloads. In the case of the Byte, Int16, SByte, and UInt16 values, the first comparison returns true because the compiler automatically performs a widening conversion and calls the Equals(Int32) method, whereas the second comparison returns false because the compiler calls the Equals(Object) method.

Notes to Callers

Compiler overload resolution may account for an apparent difference in the behavior of the two Equals(Int32) method overloads. If an implicit conversion between the obj argument and an Int32 is defined and the argument is not typed as an Object, compilers perform an implicit conversion and call the Equals(Int32) method. Otherwise, they call the Equals(Object) method, which always returns false if its obj argument is not an Int32 value. The following example illustrates the difference in behavior between the two method overloads. In the case of the Byte, Int16, SByte, and UInt16 values, the first comparison returns true because the compiler automatically performs a widening conversion and calls the Equals(Int32) method, whereas the second comparison returns false because the compiler calls the Equals(Object) method.