Björn Fahller

Finally got around to clarify the docs, and of course found a (pretty obscure) bug in the process. It's fixed on `main`. Closing now. Feel free to reopen if you...

OK, can you give some hints about information you are missing that you'd like to see, or example of information that is misleading that can be improved?

Apologies for being a bit silent, but I will get back to you in a couple of days. I much appreciate the work you're doing. Thanks.

On the libc++ build/install-script. It's only there because not all versions have readily available downloads (as .deb packages.) If setup-cpp provides the right libc++ versions already, that step can be...

I'm not so sure that it is unrelated to the PR. If you look at the "Collect Coverage" step for gcc 4.8, it says: ``` kcov: error while loading shared...

Sorry for not paying much attention, but the push to finish things before Christmas was a bit intense. I've looked into the current state, and tried to figure out how...

Of course, a different route forward, that may be easier, is to scrap `kcov` (it's not like I'm married to it) and use normal coverage builds instead. I have to...

For some reason, it never occurred to me that there's an obvious difference between warnings that are about library internals, and things that leak into user code via macros. Very...

That is because clang-tidy correctly identifies the signature of `func()` to take the `std::function` parameter by value. Unfortunately it's not clever enough to give a very helpful message, though. If...

I'm saying that `to_mock::func1()` takes a `std::function` by value i.e. it is copied, and that is what clang-tidy warns about. "wrong" is debatable, but there is nothing that can be...