function2 VS binutils-gdb

Fixed size function wrappers are not only limited and also a waste of space. Use a configurable function wrapper like fu2 with a stack allocator and set small object optimizer capacity to 0.

std::function wasn't cutting it for me, but I ended up going with fu2::function. It comes with a lot of features (almost too many), but the header size and compile times are comparable to , and it fit my needs pretty well.

Thank you, function2 is also used heavily in Idle as a type-erasure backend for continuable that is the primary asynchronous task abstraction.

You can write your own std::function, too, nor is it the only STL type that can take a capturing lambda (std::packaged_task for example).

A capturing lambda is just a class with an operator(). It's complicated to do what std::function does, but fully possible.

In fact, custom std::function replacements have better lambda support than std::function itself. Such as unique_function in https://github.com/Naios/function2 which can handle non-copyable lambdas.

function_view from binutils-gdb + it has good explanation and examples function_red by Su Brand - nice drop-in option

A bit semi-off topic, but does anyone know why, if when I checkout the source to binutils via git, I also get gdb included? (At the least on something like https://github.com/bminor/binutils-gdb)

Look on binutils+gdb or clang+llvm repos.

I think it meant uppercase .C instead of lowercase .c as a C++ extension. Indeed it's pretty rare.

That being said, there are indeed projects using lowercase .c extension for their "C++" file: gdb [1][2]

[1] https://github.com/bminor/binutils-gdb/blob/3e5fac07975a310c...

[0] : https://github.com/bminor/binutils-gdb/blob/master/gdb/guile/scm-safe-call.c