[mhogomchungu]

Problems with std::function:-

1. It can not hold move only callable objects.

2. It heap allocate stored callable object if the object is large enough.

[nly]

3. Type-erased (its primary use case, but hinders optimization)

4. Can't be constexpr

[tcbawo]

Also, std::functions are not comparable. This makes it harder to use for registration/de-registration or an Observer architecture.

[pvarangot]

I think lambdas also heap allocate, at least on embedded C++11/14 projects I remember having to have a little of heap for them.

[stargrazer]

Can you point to better alternate ways or idioms?

[MauranKilom]

It's possible to write something like `std::unique_function` (which uniquely owns the stored callable and can be moved but not copied). That's often preferable for storing functors.

Example: https://github.com/facebook/folly/blob/main/folly/docs/Funct...

[MontagFTB]

stlab has a task type that works around a couple of these issues: https://stlab.cc/libraries/concurrency/task/task/

[jjtheblunt]

(joke) : Common Lisp