The inline
specifier, when used in a function's decl-specifier-seq, declares the function to be an inline function.
A function defined entirely inside a class/struct/union definition, whether it's a member function or a non-member friend
function, is implicitly an inline function.
A function declared A deleted function is implicitly an inline function: its (deleted) definition can appear in more than one translation unit. | (since C++11) |
The A static member variable (but not a namespace-scope variable) declared | (since C++17) |
An inline function or inline variable (since C++17) has the following properties:
static
) has the following additional properties:inline
in every translation unit.In an inline function,
| (until C++17) |
Inline const variables at namespace scope have external linkage by default (unlike the non-inline non-volatile const-qualified variables). | (since C++17) |
The original intent of the inline
keyword was to serve as an indicator to the optimizer that inline substitution of a function is preferred over function call, that is, instead of executing the function call CPU instruction to transfer control to the function body, a copy of the function body is executed without generating the call. This avoids overhead created by the function call (passing the arguments and retrieving the result) but it may result in a larger executable as the code for the function has to be repeated multiple times.
Since this meaning of the keyword inline
is non-binding, compilers are free to use inline substitution for any function that's not marked inline, and are free to generate function calls to any function marked inline. Those optimization choices do not change the rules regarding multiple definitions and shared statics listed above.
Because the meaning of the keyword inline for functions came to mean "multiple definitions are permitted" rather than "inlining is preferred", that meaning was extended to variables. | (since C++17) |
If an inline function or variable (since C++17) with external linkage is defined differently in different translation units, the behavior is undefined.
The inline specifier cannot be used with a function or variable (since C++17) declaration at block scope (inside another function).
The inline specifier cannot re-declare a function or variable (since C++17) that was already defined in the translation unit as non-inline.
The implicitly-generated member functions and any member function declared as defaulted on its first declaration are inline just like any other function defined inside a class definition.
If an inline function is declared in different translation units, the accumulated sets of default arguments must be the same at the end of each translation unit.
In C, inline functions do not have to be declared inline in every translation unit (at most one may be non-inline or extern inline), the function definitions do not have to be identical (but the behavior of the program must not depend on which one is called), and the function-local statics are distinct between different definitions of the same function.
See static data members for additional rules about inline static members. Inline variables eliminate the main obstacle to packaging C++ code as header-only libraries. | (since C++17) |
// header file #ifndef EXAMPLE_H #define EXAMPLE_H // function included in multiple source files must be inline inline int sum(int a, int b) { return a + b; } #endif // source file #2 #include "example.h" int a() { return sum(1, 2); } // source file #1 #include "example.h" int b() { return sum(3, 4); }
© cppreference.com
Licensed under the Creative Commons Attribution-ShareAlike Unported License v3.0.
http://en.cppreference.com/w/cpp/language/inline