Document Links
Clickable links from source directives to their resolved target files.
Include Directives
Quoted includes
#include "..." links to the resolved header file
Every include in the file is linked, not just the preamble run at the top.
Angle-bracket includes
#include <...> links to the header found on the search path
Macro-expanded paths
#include MACRO links the directive argument to the expanded target
#include_next and __has_include_next
Standalone #include_next links back to the first matching header
first/wrap.h shadows second/wrap.h on the search path; its #include_next (guarded by __has_include_next) includes the second copy. Next-in-path resolution only exists when the header is compiled in an including TU's context — opened standalone it is compiled as its own TU, where #include_next behaves as a plain include and both links land back on the first copy.
__has_include
The checked path links to the file it probes
Embed Directives
#embed
The resource path links to the embedded file
__has_embed
The checked path links to the probed resource
Presentation
Resolved-path tooltips
Every link carries its target's absolute path as the hover tooltip
Editors render the tooltip next to the follow-link hint, e.g. /usr/include/c++/14/vector (ctrl + click).
Module Declarations
Module targets
import and module declarations do not link to interface files yet