Operator overloads allow framework types to appear as if they were built-in language primitives.
Although allowed and useful in some situations, operator overloads should be used cautiously. There are many cases in which operator overloading has been abused, such as when framework designers started to use operators for operations that should be simple methods. The following guidelines should help you decide when and how to use operator overloading.
X AVOID defining operator overloads, except in types that should feel like primitive (built-in) types.
✓ CONSIDER defining operator overloads in a type that should feel like a primitive type.
For example, System.String has
✓ DO define operator overloads in structs that represent numbers (such as System.Decimal).
X DO NOT be cute when defining operator overloads.
Operator overloading is useful in cases in which it is immediately obvious what the result of the operation will be. For example, it makes sense to be able to subtract one DateTime from another
DateTime and get a TimeSpan. However, it is not appropriate to use the logical union operator to union two database queries, or to use the shift operator to write to a stream.
X DO NOT provide operator overloads unless at least one of the operands is of the type defining the overload.
✓ DO overload operators in a symmetric fashion.
For example, if you overload the
operator==, you should also overload the
operator!=. Similarly, if you overload the
operator<, you should also overload the
operator>, and so on.
✓ CONSIDER providing methods with friendly names that correspond to each overloaded operator.
Many languages do not support operator overloading. For this reason, it is recommended that types that overload operators include a secondary method with an appropriate domain-specific name that provides equivalent functionality.
The following table contains a list of operators and the corresponding friendly method names.
|C# Operator Symbol||Metadata Name||Friendly Name|
operator == is quite complicated. The semantics of the operator need to be compatible with several other members, such as Object.Equals.
Conversion operators are unary operators that allow conversion from one type to another. The operators must be defined as static members on either the operand or the return type. There are two types of conversion operators: implicit and explicit.
X DO NOT provide a conversion operator if such conversion is not clearly expected by the end users.
X DO NOT define conversion operators outside of a type’s domain.
For example, Int32, Double, and Decimal are all numeric types, whereas DateTime is not. Therefore, there should be no conversion operator to convert a
Double(long) to a
DateTime. A constructor is preferred in such a case.
X DO NOT provide an implicit conversion operator if the conversion is potentially lossy.
For example, there should not be an implicit conversion from
Double has a wider range than
Int32. An explicit conversion operator can be provided even if the conversion is potentially lossy.
X DO NOT throw exceptions from implicit casts.
It is very difficult for end users to understand what is happening, because they might not be aware that a conversion is taking place.
✓ DO throw System.InvalidCastException if a call to a cast operator results in a lossy conversion and the contract of the operator does not allow lossy conversions.
Portions © 2005, 2009 Microsoft Corporation. All rights reserved.
Reprinted by permission of Pearson Education, Inc. from Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries, 2nd Edition by Krzysztof Cwalina and Brad Abrams, published Oct 22, 2008 by Addison-Wesley Professional as part of the Microsoft Windows Development Series.