Big libraries like Boost and OpenCV usually have meta-headers for features and components that just include all the other headers for that particular part you want to use.<p>(e.g. <a href="https:&#x2F;&#x2F;github.com&#x2F;Itseez&#x2F;opencv&#x2F;blob&#x2F;master&#x2F;include&#x2F;opencv2&#x2F;opencv.hpp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Itseez&#x2F;opencv&#x2F;blob&#x2F;master&#x2F;include&#x2F;opencv2...</a>)<p>A tool like this would see right through that and walk the tree all the way to the final leaf headers that actually implement the parts you use. This not only means one single include will balloon to many smaller ones, but when the library moves things around internally your code will break.<p>(Unclear if this is what this tool in particular will do, but I&#x27;ve certainly seen this behavior with Clion for example when it recommends what header to include.)