Extension constraints including conditional conformance

[andersio]

Not sure if I have missed something — it seems Jazzy does not generate a section title for extensions with different constraints to differentiate themselves from each other. Is that only possible by manually adding // MARK: -?

[SDGGiesbrecht]

You are correct. There is no automation for this yet.

Using // MARK: - is exactly how I do it right now. Compare this source and this output (2016‐12‐26).

I have even added this custom rule to SwiftLint so that I cannot forget to mark where‐extensions.

[reitzig]

For reference.

Input:

/// Fly, you Foos!
public struct Foo<T> {
    /// Creates a new instance with a single `T`.
    public init(t: T) {}
}

public extension Foo where T == Int {
    /// Creates a new instance with the sum of many `T`.
    public init(t: T...) {
        self.init(t: t.reduce(0, {$0 + $1}))
    }
}

Expected output: unclear, but it should be obvious that init(t: T...) is only available for some choices of T.

Actual output:

[SDGGiesbrecht]

This goes hand in hand with #if statements (#750).

[johnfairh]

I'm playing with a prototype to deal better with extensions: automatically generates sections for extension constraints as well as documenting protocol conformances added by extensions, conditional or unilateral.

So we get this kind of thing:

...with autolinking in the constraint:

Conformances from extensions are shown alongside original type declarations:

And extensions of external types use the actual extension declarations rather than the extended type:

Need to write more tests and sort out dependencies but should get here.

[johnfairh]

(finally) fixed in master.