Doxygen has syntax for this—///<—but we can probably figure it out on our own.

cc @bitjammer, @akyrtzi

To quote @gribozavr from rdar://26982593: "It was a deliberate decision to not add “trailing comments” in Swift, because when I was implementing this feature for Clang, we found a ton of nasty corner-cases and non-intuitive behavior."

How about just ignoring trailing comments, for now?

Definition of "trailing comments": Comment which is not isAtStartOfLine

Example:

decl1 /**
   trailing
*/ /** not trailing, attached to `decl2` */ decl2 /** trailing */ /// trailing
/// not trailing, attached to `decl3`

decl3

Comment by Yasuhiro Inami (JIRA)

I personally prefer:

public class C {
    public var i: Int = 1 /// FOO
    public var j: Int = 1 /** BAR */
    public var k: Int = 1
}

or

// Extra newline is added after trailing doc-comment
public class C {
    public var i: Int = 1
    /// FOO

    public var j: Int = 1
    /** BAR */

    public var k: Int = 1
}

be equivalent to this:

public class C {
    /// FOO
    public var i: Int

    /** BAR */
    public var j: Int

    public var k: Int
}

And using extra symbol e.g. `///<` seems redundant to me.

cf. https://twitter.com/inamiy/status/1058957674086260737

@swift-ci create

Comment by Yasuhiro Inami (JIRA)

Related: SR-9616

My previous comment in #comment-41118 should be modified that:

// Extra newline is added after trailing doc-comment
public class C {
    public var i: Int = 1
    /// FOO

    public var j: Int = 1
    /** BAR */

    public var k: Int = 1
}

will NOT be the case of trailing-doc-comment
because when thinking about SR-9616 syntax's trivia rule, `/// FOO` should still be owned by `public var j ...`'s leadingTrivia.