Mikael Simberg

If it does, we should rely on `BUILD_SHARED_LIBS` to choose whether to build static or shared libraries.

It's unnecessary, and in the worst case also contributes to debug bloat.

Use `\headerfile` directive in doxygen documentation to indicate public header to include for functionality

2

See https://www.doxygen.nl/manual/commands.html#cmdheaderfile.

https://clang.llvm.org/extra/clang-tidy/checks/misc/include-cleaner.html

https://clang.llvm.org/extra/clang-tidy/checks/list.html

https://scorecard.dev/

If you're new to pika development and are looking for a way to get started, we've labeled issues that could be good starting points for you. Look for the label...

https://gcc.gnu.org/gcc-14/changes.html

The public API of pika is small: sender/receiver functionality, runtime initialization, what else? Hidden functionality can then gradually be brought into the public namespace through `pika::experimental::` or directly into `pika::`....