Home > Backend Development > C++ > How Do Deleted Functions in C 11 Influence Overload Resolution?

How Do Deleted Functions in C 11 Influence Overload Resolution?

Mary-Kate Olsen
Release: 2024-12-15 15:22:24
Original
376 people have browsed it

How Do Deleted Functions in C  11 Influence Overload Resolution?

Overload Resolution in C 11 with Deleted Functions

C 11 allows for the use of the = delete syntax to mark functions as "deleted." This syntax prevents the compiler from generating the function body and prohibits its direct invocation. However, these deleted functions still participate in overload resolution, a process that determines the most appropriate function to call given a set of input parameters.

Why is this feature useful? Why are deleted functions hidden instead of being completely removed from the code?

The primary reason is to disable specific overloads based on parameter types. By participating in overload resolution, deleted functions prevent implicit conversions that could lead to unintended behavior. Consider the following example:

struct onlydouble {
  onlydouble(std::intmax_t) = delete;
  onlydouble(double);
};
Copy after login

If delete entirely removed the function, it would effectively make the = delete syntax equivalent to:

struct onlydouble2 {
  onlydouble2(double);
};
Copy after login

With this change, the following code would be legal:

onlydouble2 val(20);
Copy after login

The compiler would attempt to implicitly convert the integer literal 20 to a double before invoking the constructor that takes a double.

By contrast, in the original example with the deleted constructor, the compiler would detect an exact match between the function parameters (std::intmax_t) and the argument (20). It would then raise an error because it has selected a deleted function for invocation.

The = delete syntax, therefore, allows for stronger control over which functions are called based on parameter types. It prevents implicit conversions that could result in unintended consequences.

Additionally, the concept of "this does not exist" is not necessary in the C specification because:

  • Special grammar exists for deleting functions ("I forbid this")
  • Implicitly defined functions (e.g., copy constructor) exist by default
  • Overload resolution handles function "existence" by identifying mismatches or ambiguities
  • The primary purpose of deleted functions is to control overload resolution, rather than indicating non-existence

The above is the detailed content of How Do Deleted Functions in C 11 Influence Overload Resolution?. For more information, please follow other related articles on the PHP Chinese website!

source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Latest Articles by Author
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template