Our great sponsors
-
The tool for deal with this is https://include-what-you-use.org/
The idea is that each file (source or header) should include exactly those headers from which it uses things. In practice, it gets a bit more complicated has you don't want to include internal implementation headers and sometimes the same thing does not even have a canonical public header but IWUY does allow you to configure all that to your liking.
-
I really suggest to check out the fast and friendly Xmake that do support C20++ modules
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Tell that to cloudflare, snarky person
I don't know what tool you're using to determine this, but it'll say the same for half of the internet as my site is hosted on render.com and proxied via cloudflare.
Also, everything on this website is open source https://github.com/kjk/blog
You can read all the "secrets" you want without even visiting the site.
Related posts
- An Introduction to Modern CMake
- How to Structure C Projects: These Best Practices Worked for Me
- xmake: Fast and lightweight build tools with dependency package integration
- Xmake v2.8.5 released, Support for link sorting and unit testing
- Xmake v2.8.5 released, Support for link sorting and unit testing