Jeremy David Giesbrecht

I’ve tried to get this to work in my own project to no avail. It is easy enough to output the same syntax as `swift build` (roughly the [same as...

> I think you could set up an external build system target... @jpsim, it was a great idea. Unfortunately when I tried it (with `swift build`) there were still no...

> FYI, this fixit is entirely generated by the swift compiler, not Xcode. @masters3d, yes, the Swift compiler *defines the locations and replacements* of the fix‐its. The output of `swift...

>It *might* actually be possible to render fix-its from external build phases [...] Probably the easiest test is to have something that generates fix‐its when Xcode builds it in a...

> There is no way to comment an extension. Not in Swift proper, but Jazzy does support this. Such support is aimed at extensions to types outside the module. In...

There is nothing random here. Methods and properties (within a given scope) are in precisely the order they appear in source. You can manipulate this order to your heart’s content...

@drekka, the wildcards are an interesting new idea. One does already have a lot of control over excluding symbols by marking them with `/// :nodoc:`. Also, `--skip-undocumented` and `--min-acl` directly...

Much, but not all, of #487 (Use Without Xcode) is very relevant to Linux support. @kirbyfan64, you could have a look there an see if you can get something working.

A word of warning about `/// :nodoc:`: It is Jazzy‐only. Quick Help does not understand it. I used to use `/// :nodoc:` for overrides, but then I realized Quick Help...

@paulofaria > how can I hide :nodoc: from quick help? You can’t. If you want to satisfy Quick Help, you have to manually copy and paste the entire documentation comment...