Constructs a closure (an unnamed function object capable of capturing variables in scope).
[edit] Syntax [edit] Lambda expressions without an explicit template parameter list (possibly non-generic)[
captures ]
front-attr (optional) (
params )
specs (optional) except (optional)
{
body }
(1) [
captures ] {
body }
(2) (until C++23) [
captures ]
front-attr (optional) trailing (optional) contract-specs (optional) {
body }
(2) (since C++23) [
captures ]
front-attr (optional) except
{
body }
(3) (since C++23) [
captures ]
front-attr (optional) specs except (optional)
{
body }
(4) (since C++23) [edit] Lambda expressions with an explicit template parameter list (always generic) (since C++20) [
captures ] <
tparams >
t-requires (optional)
(
params )
specs (optional) except (optional)
{
body }
(1) [
captures ] <
tparams >
t-requires (optional) {
body }
(2) (until C++23) [
captures ] <
tparams >
t-requires (optional)
{
body }
(2) (since C++23) [
captures ] <
tparams >
t-requires (optional) front-attr (optional) except
{
body }
(3) (since C++23) [
captures ] <
tparams >
t-requires (optional) front-attr (optional) specs except (optional)
{
body }
(4) (since C++23)
1) The lambda expression with a parameter list.
2-4) The lambda expression without a parameter list.
2) The simplest syntax. back-attr cannot be applied.
3,4) back-attr can only be applied if any of specs and except is present.
[edit] Explanation captures - Specifies the entities to be captured. tparams - A non-empty comma-separated list of template parameters, used to provide names to the template parameters of a generic lambda (seeClosureType::operator()
below). t-requires - Adds constraints to tparams.
If t-requires ends with an attribute specifier sequence, the attributes in the sequence are treated as attributes in front-attr.
(since C++23) front-attr - (since C++23) An attribute specifier sequence applies to operator() of the closure type (and thus the[[noreturn]]
attribute can be used). params - The parameter list of operator() of the closure type.
It can have an explicit object parameter.
(since C++23) specs - A list of the following specifiers, each specifier is allowed at most once in each sequence. Specifier Effect mutable Allows body to modify the objects captured by copy, and to call their non-const member functions.[[noreturn]]
attribute cannot be used). trailing - ->
ret, where ret specifies the return type. requires - (since C++20) Adds constraints to operator() of the closure type. contract-specs - (since C++26) A list of function contract specifiers for operator() of the closure type. body - The function body.
If auto
is used as a type of a parameter or an explicit template parameter list is provided(since C++20), the lambda is a generic lambda.
A variable __func__ is implicitly defined at the beginning of body, with semantics as described here.
[edit] Closure typeThe lambda expression is a prvalue expression of unique unnamed non-union non-aggregate class type, known as closure type, which is declared (for the purposes of ADL) in the smallest block scope, class scope, or namespace scope that contains the lambda expression.
The closure type is a structural type if and only if captures is empty.
(since C++20)The closure type has the following members, they cannot be explicitly instantiated, explicitly specialized, or(since C++14) named in a friend declaration:
ClosureType::operator()(params)ret operator()(params) { body }
(static and const may be present, see below)template<template-params>
ret operator()(params) { body }
Executes the body of the lambda expression, when invoked. When accessing a variable, accesses its captured copy (for the entities captured by copy), or the original object (for the entities captured by reference).
The parameter list of operator() is params if it is provided, otherwise the parameter list is empty.
The return type of operator() is the type specified in trailing .
If trailing is not provided, the return type of operator() is automatically deduced.[1]
Unless the keyword mutable was used in the lambda specifiers, or an explicit object parameter is present(since C++23), the cv-qualifier of operator() is const and the objects that were captured by copy are non-modifiable from inside this operator(). Explicit const qualifier is not allowed. operator() is never virtual and cannot have the volatile qualifier.
operator() is always constexpr if it satisfies the requirements of a constexpr function. It is also constexpr if the keyword constexpr was used in the lambda specifiers.
(since C++17)operator() is an immediate function if the keyword consteval was used in the lambda specifiers.
(since C++20)operator() is a static member function if the keyword static was used in the lambda specifiers.
operator() is an explicit object member function if params contains an explicit object parameter.
(since C++23)For each parameter in params whose type is specified as auto, an invented template parameter is added to template-params, in order of appearance. The invented template parameter may be a parameter pack if the corresponding function member of params is a function parameter pack.
// generic lambda, operator() is a template with two parameters auto glambda = [](auto a, auto&& b) { return a < b; }; bool b = glambda(3, 3.14); // OK // generic lambda, operator() is a template with one parameter auto vglambda = [](auto printer) { return [=](auto&&... ts) // generic lambda, ts is a parameter pack { printer(std::forward<decltype(ts)>(ts)...); // nullary lambda (takes no parameters): return [=] { printer(ts...); }; }; }; auto p = vglambda([](auto v1, auto v2, auto v3) { std::cout << v1 << v2 << v3; }); auto q = p(1, 'a', 3.14); // outputs 1a3.14 q(); // outputs 1a3.14(since C++14)
If the lambda definition uses an explicit template parameter list, that template parameter list is used with operator(). For each parameter in params whose type is specified as auto, an additional invented template parameter is appended to the end of that template parameter list:
// generic lambda, operator() is a template with two parameters auto glambda = []<class T>(T a, auto&& b) { return a < b; }; // generic lambda, operator() is a template with one parameter pack auto f = []<typename... Ts>(Ts&&... ts) { return foo(std::forward<Ts>(ts)...); };(since C++20)
The exception specification except on the lambda expression applies to operator().
For the purpose of name lookup, determining the type and value of the this pointer and for accessing non-static class members, the body of the closure type's operator() is considered in the context of the lambda expression.
struct X { int x, y; int operator()(int); void f() { // the context of the following lambda is the member function X::f [=]() -> int { return operator()(this->x + y); // X::operator()(this->x + (*this).y) // this has type X* }; } };Dangling references
If a non-reference entity is captured by reference, implicitly or explicitly, and operator() of the closure object is invoked after the entity's lifetime has ended, undefined behavior occurs. The C++ closures do not extend the lifetimes of objects captured by reference.
Same applies to the lifetime of the current *this object captured via this
.
capture-less non-generic lambda
using F = ret(*)(params);
operator F() const noexcept;
using F = ret(*)(params);
constexpr operator F() const noexcept;
capture-less generic lambda
template<template-params> using fptr_t = /* see below */;template<template-params>
template<template-params>
This user-defined conversion function is only defined if the lambda expression has no captures and has no explicit object parameter(since C++23). It is a public, constexpr,(since C++17) non-virtual, non-explicit, const noexcept member function of the closure object.
This function is an immediate function if the function call operator (or specialization, for generic lambdas) is an immediate function.
(since C++20)A generic capture-less lambda has a user-defined conversion function template with the same invented template parameter list as operator().
void f1(int (*)(int)) {} void f2(char (*)(int)) {} void h(int (*)(int)) {} // #1 void h(char (*)(int)) {} // #2 auto glambda = [](auto a) { return a; }; f1(glambda); // OK f2(glambda); // error: not convertible h(glambda); // OK: calls #1 since #2 is not convertible int& (*fpi)(int*) = [](auto* a) -> auto& { return *a; }; // OK(since C++14)
The value returned by the conversion function is a pointer to a function with C++ language linkage that, when invoked, has the same effect as invoking the closure type's function call operator on a default-constructed instance of the closure type.
(until C++14)The value returned by the conversion function (template) is a pointer to a function with C++ language linkage that, when invoked, has the same effect as:
The value returned by the conversion function (template) is
This function is constexpr if the function call operator (or specialization, for generic lambdas) is constexpr.
auto Fwd = [](int(*fp)(int), auto a) { return fp(a); }; auto C = [](auto a) { return a; }; static_assert(Fwd(C, 3) == 3); // OK auto NC = [](auto a) { static int s; return a; }; static_assert(Fwd(NC, 3) == 3); // error: no specialization can be // constexpr because of static s
If the closure object's operator() has a non-throwing exception specification, then the pointer returned by this function has the type pointer to noexcept function.
(since C++17) ClosureType::ClosureType()ClosureType() = default;
(since C++20)ClosureType(const ClosureType&) = default;
ClosureType(ClosureType&&) = default;
Closure types are not DefaultConstructible. Closure types have no default constructor.
(until C++20)If no captures are specified, the closure type has a defaulted default constructor. Otherwise, it has no default constructor (this includes the case when there is a capture-default , even if it does not actually capture anything).
(since C++20)The copy constructor and the move constructor are declared as defaulted and may be implicitly-defined according to the usual rules for copy constructors and move constructors.
ClosureType::operator=(const ClosureType&)ClosureType& operator=(const ClosureType&) = delete;
(until C++20)ClosureType& operator=(const ClosureType&) = default;
ClosureType& operator=(ClosureType&&) = default;
ClosureType& operator=(const ClosureType&) = delete;
(since C++20)The copy assignment operator is defined as deleted (and the move assignment operator is not declared). Closure types are not CopyAssignable.
(until C++20)If no captures are specified, the closure type has a defaulted copy assignment operator and a defaulted move assignment operator. Otherwise, it has a deleted copy assignment operator (this includes the case when there is a capture-default , even if it does not actually capture anything).
(since C++20) ClosureType::~ClosureType()~ClosureType() = default;
The destructor is implicitly-declared.
ClosureType::CapturesIf the lambda expression captures anything by copy (either implicitly with capture clause [=]
or explicitly with a capture that does not include the character &, e.g. [a, b, c]
), the closure type includes unnamed non-static data members, declared in unspecified order, that hold copies of all entities that were so captured.
Those data members that correspond to captures without initializers are direct-initialized when the lambda expression is evaluated. Those that correspond to captures with initializers are initialized as the initializer requires (could be copy- or direct-initialization). If an array is captured, array elements are direct-initialized in increasing index order. The order in which the data members are initialized is the order in which they are declared (which is unspecified).
The type of each data member is the type of the corresponding captured entity, except if the entity has reference type (in that case, references to functions are captured as lvalue references to the referenced functions, and references to objects are captured as copies of the referenced objects).
For the entities that are captured by reference (with the capture-default [&]
or when using the character &, e.g. [&a, &b, &c]
), it is unspecified if additional data members are declared in the closure type, but any such additional members must satisfy LiteralType(since C++17).
The captures defines the outside variables that are accessible from within the lambda function body. Its syntax is defined as follows:
capture-default (1) capture-list (2) capture-default,
capture-list (3) capture-default - one of &
and =
capture-list - a comma-separated list of capture s
The syntax of capture is defined as follows:
...
(2) identifier initializer (3) (since C++14) &
identifier (4) &
identifier ...
(5) &
identifier initializer (6) (since C++14) this
(7) *
this
(8) (since C++17) ...
identifier initializer (9) (since C++20) &
...
identifier initializer (10) (since C++20)
1) simple by-copy capture
4) simple by-reference capture
6) by-reference capture with an initializer
7) simple by-reference capture of the current object
8) simple by-copy capture of the current object
9) by-copy capture with an initializer that is a pack expansion
10) by-reference capture with an initializer that is a pack expansion
If the capture-default is &
, subsequent simple captures must not begin with &
.
struct S2 { void f(int i); }; void S2::f(int i) { [&] {}; // OK: by-reference capture default [&, i] {}; // OK: by-reference capture, except i is captured by copy [&, &i] {}; // Error: by-reference capture when by-reference is the default [&, this] {}; // OK, equivalent to [&] [&, this, i] {}; // OK, equivalent to [&, i] }
If the capture-default is =
, subsequent simple captures must begin with &
or be *this
(since C++17) or this
(since C++20).
struct S2 { void f(int i); }; void S2::f(int i) { [=] {}; // OK: by-copy capture default [=, &i] {}; // OK: by-copy capture, except i is captured by reference [=, *this] {}; // until C++17: Error: invalid syntax // since C++17: OK: captures the enclosing S2 by copy [=, this] {}; // until C++20: Error: this when = is the default // since C++20: OK, same as [=] }
Any capture may appear only once, and its name must be different from any parameter name:
struct S2 { void f(int i); }; void S2::f(int i) { [i, i] {}; // Error: i repeated [this, *this] {}; // Error: "this" repeated (C++17) [i] (int i) {}; // Error: parameter and capture have the same name }
A lambda expression can use a variable without capturing it if the variable
A lambda expression can read the value of a variable without capturing it if the variable
The current object (*this) can be implicitly captured if either capture default is present. If implicitly captured, it is always captured by reference, even if the capture default is =
. The implicit capture of *this when the capture default is =
is deprecated.(since C++20)
Only lambda expressions satisfying any of the following conditions may have a capture-default or capture without initializers:
For such lambda expression, the reaching scope is defined as the set of enclosing scopes up to and including the innermost enclosing function (and its parameters). This includes nested block scopes and the scopes of enclosing lambdas if this lambda is nested.
The identifier in any capture without an initializer (other than the this
-capture) is looked up using usual unqualified name lookup in the reaching scope of the lambda. The result of the lookup must be a variable with automatic storage duration declared in the reaching scope, or a structured binding whose corresponding variable satisfies such requirements(since C++20). The entity is explicitly captured.
A capture with an initializer, called init-capture, acts as if it declares and explicitly captures a variable declared with type specifier auto
and the same initializer, whose declarative region is the body of the lambda expression (that is, it is not in scope within its initializer), except that:
This is used to capture move-only types with a capture such as x = std::move(x).
This also makes it possible to capture by const reference, with &cr = std::as_const(x) or similar.
int x = 4; auto y = [&r = x, x = x + 1]() -> int { r += 2; return x * x; }(); // updates ::x to 6 and initializes y to 25.(since C++14)
If captures has a capture-default and does not explicitly capture the enclosing object (as this or *this), or an automatic variable that is odr-usable in the lambda body, or a structured binding whose corresponding variable has atomic storage duration(since C++20), it captures the entity implicitly if the entity is named in a potentially-evaluated expression within an expression (including when the implicit this-> is added before a use of non-static class member).
For the purpose of determining implicit captures, typeid
is never considered to make its operands unevaluated.
Entities might be implicitly captured even if they are only named within a discarded statement after instantiation of the lambda body.
(since C++17)void f(int, const int (&)[2] = {}) {} // #1 void f(const int&, const int (&)[1]) {} // #2 struct NoncopyableLiteralType { constexpr explicit NoncopyableLiteralType(int n) : n_(n) {} NoncopyableLiteralType(const NoncopyableLiteralType&) = delete; int n_; }; void test() { const int x = 17; auto l0 = []{ f(x); }; // OK: calls #1, does not capture x auto g0 = [](auto a) { f(x); }; // same as above auto l1 = [=]{ f(x); }; // OK: captures x (since P0588R1) and calls #1 // the capture can be optimized away auto g1 = [=](auto a) { f(x); }; // same as above auto ltid = [=]{ typeid(x); }; // OK: captures x (since P0588R1) // even though x is unevaluated // the capture can be optimized away auto g2 = [=](auto a) { int selector[sizeof(a) == 1 ? 1 : 2] = {}; f(x, selector); // OK: is a dependent expression, so captures x }; auto g3 = [=](auto a) { typeid(a + x); // captures x regardless of // whether a + x is an unevaluated operand }; constexpr NoncopyableLiteralType w{42}; auto l4 = []{ return w.n_; }; // OK: w is not odr-used, capture is unnecessary // auto l5 = [=]{ return w.n_; }; // error: w needs to be captured by copy }
If the body of a lambda odr-uses an entity captured by copy, the member of the closure type is accessed. If it is not odr-using the entity, the access is to the original object:
void f(const int*); void g() { const int N = 10; [=] { int arr[N]; // not an odr-use: refers to g's const int N f(&N); // odr-use: causes N to be captured (by copy) // &N is the address of the closure object's member N, not g's N }(); }
If a lambda odr-uses a reference that is captured by reference, it is using the object referred-to by the original reference, not the captured reference itself:
#include <iostream> auto make_function(int& x) { return [&] { std::cout << x << '\n'; }; } int main() { int i = 3; auto f = make_function(i); // the use of x in f binds directly to i i = 5; f(); // OK: prints 5 }
Within the body of a lambda with capture default =
, the type of any capturable entity is as if it were captured (and thus const-qualification is often added if the lambda is not mutable), even though the entity is in an unevaluated operand and not captured (e.g. in decltype
):
void f3() { float x, &r = x; [=] { // x and r are not captured (appearance in a decltype operand is not an odr-use) decltype(x) y1; // y1 has type float decltype((x)) y2 = y1; // y2 has type float const& because this lambda // is not mutable and x is an lvalue decltype(r) r1 = y1; // r1 has type float& (transformation not considered) decltype((r)) r2 = y2; // r2 has type float const& }; }
Any entity captured by a lambda (implicitly or explicitly) is odr-used by the lambda expression (therefore, implicit capture by a nested lambda triggers implicit capture in the enclosing lambda).
All implicitly-captured variables must be declared within the reaching scope of the lambda.
If a lambda captures the enclosing object (as this or *this), either the nearest enclosing function must be a non-static member function or the lambda must be in a default member initializer:
struct s2 { double ohseven = .007; auto f() // nearest enclosing function for the following two lambdas { return [this] // capture the enclosing s2 by reference { return [*this] // capture the enclosing s2 by copy (C++17) { return ohseven;â// OK } }(); } auto g() { return [] // capture nothing { return [*this] {};â// error: *this not captured by outer lambda expression }(); } };
If a lambda expression (or a specialization of a generic lambda's function call operator)(since C++14) ODR-uses *this or any variable with automatic storage duration, it must be captured by the lambda expression.
void f1(int i) { int const N = 20; auto m1 = [=] { int const M = 30; auto m2 = [i] { int x[N][M]; // N and M are not odr-used // (ok that they are not captured) x[0][0] = i; // i is explicitly captured by m2 // and implicitly captured by m1 }; }; struct s1 // local class within f1() { int f; void work(int n) // non-static member function { int m = n * n; int j = 40; auto m3 = [this, m] { auto m4 = [&, j] // error: j is not captured by m3 { int x = n; // error: n is implicitly captured by m4 // but not captured by m3 x += m; // OK: m is implicitly captured by m4 // and explicitly captured by m3 x += i; // error: i is outside of the reaching scope // (which ends at work()) x += f; // OK: this is captured implicitly by m4 // and explicitly captured by m3 }; }; } }; }
Class members cannot be captured explicitly by a capture without initializer (as mentioned above, only variables are permitted in the capture-list ):
class S { int x = 0; void f() { int i = 0; // auto l1 = [i, x] { use(i, x); }; // error: x is not a variable auto l2 = [i, x = x] { use(i, x); }; // OK, copy capture i = 1; x = 1; l2(); // calls use(0,0) auto l3 = [i, &x = x] { use(i, x); }; // OK, reference capture i = 2; x = 2; l3(); // calls use(1,2) } };
When a lambda captures a member using implicit by-copy capture, it does not make a copy of that member variable: the use of a member variable m
is treated as an expression (*this).m, and *this is always implicitly captured by reference:
class S { int x = 0; void f() { int i = 0; auto l1 = [=] { use(i, x); }; // captures a copy of i and // a copy of the this pointer i = 1; x = 1; l1(); // calls use(0, 1), as if // i by copy and x by reference auto l2 = [i, this] { use(i, x); }; // same as above, made explicit i = 2; x = 2; l2(); // calls use(1, 2), as if // i by copy and x by reference auto l3 = [&] { use(i, x); }; // captures i by reference and // a copy of the this pointer i = 3; x = 2; l3(); // calls use(3, 2), as if // i and x are both by reference auto l4 = [i, *this] { use(i, x); }; // makes a copy of *this, // including a copy of x i = 4; x = 4; l4(); // calls use(3, 2), as if // i and x are both by copy } };
If a lambda expression appears in a default argument, it cannot explicitly or implicitly capture anything, unless all captures have initializers which satisfy the constraints of an expression appearing in a default argument(since C++14):
void f2() { int i = 1; void g1( int = [i] { return i; }() ); // error: captures something void g2( int = [i] { return 0; }() ); // error: captures something void g3( int = [=] { return i; }() ); // error: captures something void g4( int = [=] { return 0; }() ); // OK: capture-less void g5( int = [] { return sizeof i; }() ); // OK: capture-less // C++14 void g6( int = [x = 1] { return x; }() ); // OK: 1 can appear // in a default argument void g7( int = [x = i] { return x; }() ); // error: i cannot appear // in a default argument }
Members of anonymous unions members cannot be captured. Bit-fields can only be captured by copy.
If a nested lambda m2
captures something that is also captured by the immediately enclosing lambda m1
, then m2
's capture is transformed as follows:
m1
captures by copy, m2
is capturing the non-static member of m1
's closure type, not the original variable or *this; if m1
is not mutable, the non-static data member is considered to be const-qualified.m1
captures by reference, m2
is capturing the original variable or *this.#include <iostream> int main() { int a = 1, b = 1, c = 1; auto m1 = [a, &b, &c]() mutable { auto m2 = [a, b, &c]() mutable { std::cout << a << b << c << '\n'; a = 4; b = 4; c = 4; }; a = 3; b = 3; c = 3; m2(); }; a = 2; b = 2; c = 2; m1(); // calls m2() and prints 123 std::cout << a << b << c << '\n'; // prints 234 }
If a lambda captures anything, the type of the explicit object parameter (if any) of the function call operator can only be
struct C { template<typename T> C(T); }; void func(int i) { int x = [=](this auto&&) { return i; }(); // OK int y = [=](this C) { return i; }(); // error int z = [](this C) { return 42; }(); // OK auto lambda = [n = 42] (this auto self) { return n; }; using Closure = decltype(lambda); struct D : private Closure { D(Closure l) : Closure(l) {} using Closure::operator(); friend Closure; }; D{lambda}(); // error }(since C++23) [edit] Notes
The rule for implicit lambda capture is slightly changed by defect report P0588R1. As of 2023-10, some major implementations have not completely implemented the DR, and thus the old rule, which detects odr-using, is still used in some cases.
Old rule before P0588R1If captures has a capture-default and does not explicitly capture the enclosing object (as this
or *this
), or an automatic variable that is odr-usable in the lambda body, or a structured binding whose corresponding variable has atomic storage duration(since C++20), it captures the entity implicitly if the entity is
This example shows how to pass a lambda to a generic algorithm and how objects resulting from a lambda expression can be stored in std::function objects.
#include <algorithm> #include <functional> #include <iostream> #include <vector> int main() { std::vector<int> c{1, 2, 3, 4, 5, 6, 7}; int x = 5; c.erase(std::remove_if(c.begin(), c.end(), [x](int n) { return n < x; }), c.end()); std::cout << "c: "; std::for_each(c.begin(), c.end(), [](int i) { std::cout << i << ' '; }); std::cout << '\n'; // the type of a closure cannot be named, but can be inferred with auto // since C++14, lambda could own default arguments auto func1 = [](int i = 6) { return i + 4; }; std::cout << "func1: " << func1() << '\n'; // like all callable objects, closures can be captured in std::function // (this may incur unnecessary overhead) std::function<int(int)> func2 = [](int i) { return i + 4; }; std::cout << "func2: " << func2(6) << '\n'; constexpr int fib_max {8}; std::cout << "Emulate `recursive lambda` calls:\nFibonacci numbers: "; auto nth_fibonacci = [](int n) { std::function<int(int, int, int)> fib = [&](int n, int a, int b) { return n ? fib(n - 1, a + b, a) : b; }; return fib(n, 0, 1); }; for (int i{1}; i <= fib_max; ++i) std::cout << nth_fibonacci(i) << (i < fib_max ? ", " : "\n"); std::cout << "Alternative approach to lambda recursion:\nFibonacci numbers: "; auto nth_fibonacci2 = [](auto self, int n, int a = 0, int b = 1) -> int { return n ? self(self, n - 1, a + b, a) : b; }; for (int i{1}; i <= fib_max; ++i) std::cout << nth_fibonacci2(nth_fibonacci2, i) << (i < fib_max ? ", " : "\n"); #ifdef __cpp_explicit_this_parameter std::cout << "C++23 approach to lambda recursion:\n"; auto nth_fibonacci3 = [](this auto self, int n, int a = 0, int b = 1) -> int { return n ? self(n - 1, a + b, a) : b; }; for (int i{1}; i <= fib_max; ++i) std::cout << nth_fibonacci3(i) << (i < fib_max ? ", " : "\n"); #endif }
Possible output:
c: 5 6 7 func1: 10 func2: 10 Emulate `recursive lambda` calls: Fibonacci numbers: 0, 1, 1, 2, 3, 5, 8, 13 Alternative approach to lambda recursion: Fibonacci numbers: 0, 1, 1, 2, 3, 5, 8, 13[edit] Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR Applied to Behavior as published Correct behavior CWG 974 C++11 default argument was not allowed in theauto
specifier (C++11) specifies a type deduced from an expression [edit] copyable wrapper of any copy constructible callable object
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4