I'm lacking the imagination how the visuals for this could look like.

One idea: We could use the type names display the operators with their type names. E.g. we would display an infix operator == then like LeftType == RightType, a prefix operator <-- would become <--Type and a postfix operator --> would become Type-->.

However, this omits the return type of the operation, but the return type might be rather important for custom DSLs with custom operators.

Regarding the implementation then: My current approach simply changed the name property which we introduced in an extension on Function. This does not feel right for doing this. How do you feel about introducing a displayedNamed property?

Also, it's rather easy to distinguish between prefix, infix and postfix operators. The first and the latter always need to have a modifier in the method implementation. But should we add this kind of logic into swift-doc or should we extend SwiftSemantics?

Thanks again for taking a stab at this, @Lukas-Stuehrk.

After digging into this a bit more, I realized that I'd originally conflated operators with functions that implement an operator. This became a lot clearer when I tried running swift-doc on Euler.

To clarify, this is an operator:

infix operator ≈ : ComparisonPrecedence

...and this is a function implementing that operator:

public func ≈ <T>(lhs: T, rhs: T) -> Bool where T : FloatingPoint {
    return lhs == rhs || lhs.nextDown == rhs || lhs.nextUp == rhs
}

I think your change is the correct — functions that implement an operator should be grouped in type pages.

My latest changes build on this by doing the following:

• Update SourceFile to collect OperatorDecl syntax nodes
• Create a new OperatorPage, which names implementations according to their operands (e.g. func ==(lhs: Int, rhs: Int) is shown as Int == Int)
• Distinguish between infix, prefix, and postfix operators
• Change the home page to order operators by their kind (prefix, etc.)

I also updated the CSS to add a custom style for operators. Here's what all of that looks like:

Operator page:

Home page: