examc VS templight

There are other ways to do this. I made a proof of concept of using linker sections to allow you to sprinkle tests within the implementation inline once... https://github.com/cozzyd/examc (this is obviously not production-ready, just serves as a proof of concept).

Basically the idea is that the test code gets written to a different linker section that your test runner can iterate through, when tests are enabled.

Indeed, I just made a POC with compiler sections: https://github.com/cozzyd/examc

This implementation only works with gcc though probably (it uses the automatic __start_SECTION and __stop_SECTION that gcc generates but clang doesn't seem to... there are likely hacks to make this work anyway though).

IMHO the best approach is to avoid the problem by applying TDD. Then there is very little need to debug anything. But otherwise, there is https://github.com/mikael-s-persson/templight for compile-time debugging which is pretty cool and having something like `expect(auto... args) static_asert(args...); assert(args...);` may help with being able to debug at run-time and get the coverage (though, the code has has to compile aka pass first).

For sure. There has been https://github.com/mikael-s-persson/templight and https://github.com/metashell/metashell. The former allowed to basically step into the compilation process (after the fact).

Double not sure whether practical, though, https://github.com/mikael-s-persson/templight approched the problem back in the day

Is there a function in lsp-mode, or ccls directly to find the compilation command associated with the file (if any) in the current buffer? If not, would another package (rtags, ede-compdb, irony-cdb) help query the compilation database without needing to use the rest of the package? The main use case is to plug it into other tools such as rmsbolt and templight that "compile" code to provide additional information.