As a possible drawback, note that passing by copy could not work if the lambda isn’t copyable. If you can get away with it, passing by copy is just fine.
As an example:
#include<memory>
#include<utility>
template<typename F>
void g(F &&f) {
std::forward<F>(f)();
}
template<typename F>
void h(F f) {
f();
}
int main() {
auto lambda = [foo=std::make_unique<int>()](){};
g(lambda);
//h(lambda);
}
In the snippet above, lambda
isn’t copyable because of foo
. Its copy constructor is deleted as a consequence of the fact that the copy constructor of a std::unique_ptr
is deleted.
On the other side, F &&f
accepts both lvalue and rvalue references being it a forwarding reference, as well as const references.
In other terms, if you want to reuse the same lambda as an argument more than once, you cannot if your functions get your object by copy and you must move it for it’s not copyable (well, actually you can, it’s a matter of wrapping it in a lambda that captures the outer one by reference).