Barton–Nackman trick

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Barton–Nackman trick is a term coined by the C++ standardization committee (ISO/IEC JTC1/SC22 WG21) to refer to an idiom introduced by John Barton and Lee Nackman as Restricted Template Expansion.[1]

The idiom[edit]

The idiom is characterized by an in-class friend function definition appearing in the base class template component of the Curiously Recurring Template Pattern (CRTP).

// A class template to express an equality comparison interface.
template<typename T> class equal_comparable {
    friend bool operator==(T const &a, T const &b) { return  a.equal_to(b); }
    friend bool operator!=(T const &a, T const &b) { return !a.equal_to(b); }
};
 
class value_type
 // Class value_type wants to have == and !=, so it derives from
 // equal_comparable with itself as argument (which is the CRTP).
 : private equal_comparable<value_type> {
  public:
    bool equal_to(value_type const& rhs) const; // to be defined
};

When a class template like equal_comparable is instantiated, the in-class friend definitions produce nontemplate (and nonmember) functions (operator functions in this case). At the time the idiom was introduced (1994) the C++ language did not define a partial ordering for overloaded function templates and as a result overloading function templates often resulted in ambiguities. For example, trying to capture a generic definition for operator== as

template<typename T>
bool operator==(T const &a, T const &b) {
    /* ... */
}

would essentially be incompatible with another definition like

template<typename T>
bool operator==(Array<T> const &a, Array<T> const &b) {
    /* ... */
}

The Barton–Nackman trick, then, achieves the goal of providing a generic user-defined equality operator without having to deal with such ambiguities. The adjective restricted in the idiom name refers to the fact that the provided in-class function definition is restricted (only applies) to specializations of the given class template.

The term is sometimes mistakenly used to refer to the Curiously Recurring Template Pattern (CRTP). As explained above, the Barton–Nackman trick is a distinct idiom (that relies on the CRTP).

How it works[edit]

When the compiler encounters the expression

v1 == v2

where v1 and v2 are of type value_type, it attempts argument-dependent lookup (ADL) for operator==. This lookup includes consideration of friend functions declared in value_type and its base classes. (Note that if value_type were an incomplete template instance, ADL would trigger its complete instantiation.)

The Barton–Nackman trick originally relied not on ADL but on a C++ feature called "friend name injection", in which an in-class declaration of a friend function made the function name visible in the immediately surrounding namespace scope (possibly the global scope). When investigating the possibility of removing friend name injection from the C++ programming language, Barton and Nackman's idiom was found to be the only reasonable use of that language rule. Eventually, the rules for argument-dependent lookup were adjusted[2] to replace friend name injection by a less drastic mechanism, described above, that maintained the validity of Barton and Nackman's technique. It is worth noting that, as a consequence of this change, the expression

::operator==(v1,v2)

is no longer valid, because qualified names aren't subject to ADL and friend declarations aren't found via ordinary lookup. Note that this implies that the friend specifier is essential, even if the defined friend functions do not actually need to access nonpublic members of the befriending class.

Proposed replacement[edit]

The C++0x Concepts generic programming specification would have made obsolete the Barton–Nackman trick, though Concepts have since been removed from the final C++11 language standard.[3]

See also[edit]

References[edit]

  1. ^ Barton, John J.; Nackman, Lee R. (1994). Scientific and Engineering C++: An Introduction with Advanced Techniques and Examples. Addison-Wesley Professional. ISBN 0-201-53393-6. 
  2. ^ "An Alternative to Name Injection from Templates" (PDF). An Alternative to Name Injection from Templates. Retrieved April 12, 2005. 
  3. ^ Siek et al., "Concepts for C++0x", document no. N1758 [1] p. 38.

Further reading[edit]

  • Vandevoorde, David; Nicolai M. Josuttis (2002). C++ Templates: The Complete Guide. Addison-Wesley Professional. ISBN 0-201-73484-2.