Approaches for multiple extension block doccomments

[taylorswift]

@xwu

My point above was that the proposed behavior here would, in the scenarios I outline above, produce worse (actively misleading, thus incorrect) output than just dropping the comments on the floor, what you label as “just unsupported.”

the “proposed” behavior here is to preserve doccomments for each extension (multiple blocks, same generic signature), the current DocC behavior drops all (but one comment) on the floor. the “proposed” behavior would preserve more, but not all, of the possible doccomments.

@xwu

Not that I am arguing for unnecessary bloat, but preferencing storage compactness (a factor you cite above) in a discussion about information presentation is an inversion of priorities, I would think, and we really shouldn’t need to be inventing ersatz compression heuristics.

maybe skim the transcript of Swift Package Indexing | Transcript: 19: The SPI project is growing up, DocC uploading with AWS Lambda, and Are we server yet? it is a real problem without good solutions at the moment, and i have also personally spent a lot of effort trying to work around it.

@xwu

For clarity, are you saying that empty extension blocks are already common?

i am saying i think it is likely to become common very soon, now that Enablement of DocC Extension Support as Default in Swift 5.9 has landed.

your argument is essentially that this launch is premature and the feature is not ready for release. while i was not present for the vote on monday, i think it’s fair to say that ship has already sailed.