Answer

SFINAE (Substitution Failure Is Not An Error) is a key mechanism of template specialization in C++. If the definition becomes invalid during template selection (for example, when type substitution leads to an error at the template selection stage), it is not a compilation error, but simply makes the template unavailable for selection.

SFINAE is the basis for tools like std::enable_if, various type detectors (type traits), and implements the tag dispatching pattern.

Correct example:

#include <type_traits>

// For integers
template<typename T>
typename std::enable_if<std::is_integral<T>::value, void>::type foo(T) {
    std::cout << "Integral
";
}
// For others
template<typename T>
typename std::enable_if<!std::is_integral<T>::value, void>::type foo(T) {
    std::cout << "Not integral
";
}

Incorrect usage: One might accidentally end up with overload ambiguity or trigger a compilation error if the conditions for std::enable_if or specialization are described carelessly.

Trick question

Can SFINAE be used to choose between overloads of regular (non-template) functions?

Answer: No, SFINAE only applies to function or class templates. It does not work for regular overloaded functions. It is often mistakenly attempted to write std::enable_if in the parameters of a regular function, which does not lead to selection, but simply makes the signature undefined.

Example of the erroneous variant:

void foo(int, typename std::enable_if<true, int>::type* = nullptr) {} // Error: not a template

Examples of real errors due to ignorance of the topic nuances

---

Story

In a serialization library, while implementing template functions with SFINAE, the intersection of conditions for two specializations was mistakenly overlooked. The result was an ambiguous overload situation and the inability to compile the module with the emergence of a new data type.

---

---

Story

In the old code of the library boost::asio, due to an erroneous implementation of SFINAE (through dependent false in static_assert), error messages appeared that were unreadable: the compiler expanded all templates instead of removing incorrect options. This was fixed by using separate enable_if at the signature level.

---

---

Story

When porting type-based search algorithms using SFINAE to an old compiler (MSVC 2012), the team encountered that type decomposition was incorrect, and the selected template accepted the wrong type. The check was resolved using type traits before compilation, eliminating substitution in the template itself.

---