Build systems can use such feature, without going through heavy duty isolation (sandboxing) like Bazel. It's done there, such that "accidental" dependencies ar

Build systems can use such feature, without going through heavy duty isolation (sandboxing) like Bazel. It's done there, such that "accidental" dependencies are not followed, e.g. if your a.cpp source included b.h it better be that the rule compiling a.cpp explicitly stated that is dependent on a rule "exporting" b.h And possibly for other uses too :)