they are not relevant in documentation, but SymbolGraphGen isn’t a documentation generator, it’s a serializer whose outputs documentation generators use to generate documentation. the holes in the symbol graphs are a major problem for such tooling (including swift-biome) because they impede certain optimizatons and break invariants that they rely on in order to serve large amounts of documentation at scale. although the end consumer of documentation will never see the hidden APIs, they are important for the tooling’s internal data model.
for example, swift-biome currently de-duplicates synthesized members against their generic base, since not doing so leads to quadratic explosion of synthesized symbols when protocols contain many extension members (like Sequence) and also have many conformers (like Sequence). this is part of the reason why SwiftSyntax’s symbol graph is 2 orders of magnitude larger than a typical library. however, this optimization is not possible if swift-biome doesn’t know about the generic base in the first place, because it was part of an underscored API.
yeah, i can implement it in a PR, i was just asking here to see if this was a change that has a good chance of getting accepted.
i don’t know where the issue tracker for SymbolGraphGen lives. should i just file it on bugs.swift.org as a compiler issue?