Mattt

@karwa Thanks for sharing your feedback about the design. I agree that matters of style can be difficult to discuss because of their subjective nature. There's a consensus among designers...

Honestly, I think this is something we should solve at the language level. It looks like you could avoid the redundant namespace by using the [`@warn_unqualified_access`](https://docs.swift.org/swift-book/ReferenceManual/Attributes.html#ID598) annotation. Unfortunately, this only...

@muizidn I wouldn't consider PDF to be a primary output format for `swift-doc`. Instead, I'd recommend using a tool like [PrinceXML](https://www.princexml.com) to generate PDF from HTML + CSS.

There are examples of programming languages working really well for configuration (Homebrew formulas), and there are examples where a programming language would have been preferable (pretty much any configuration system...

See also https://github.com/apple/swift-argument-parser/issues/41

Related to #31. Alternatively, we can use the collected `import` statements for a symbol's source file to narrow candidates.

Since this is unlikely to happen and it's unclear what the correct should be, the best course of action would be to log a warning.

Thanks for writing this up, @kean. I agree that this is something we should do, and it's something I've been thinking about a lot. And when I say "thinking about",...

@compnerd I'm unfamiliar with how Windows Installer works, so apologies for asking some really basic questions: - Are `.msi` files self-contained? That is, can a user install `swift-doc` by downloading...

> Well, it would be semi-self-contained. Yes, a user would be able to download and "open" one to install. But the expectation would be that they would be responsible for...