If class has primary constructor, cannot provide XML documentation comment for class

[SetTrend]

Version Used: .NET 8.0

Steps to Reproduce:

1. Create a class with primary constructor
2. Add XML documentation to primary constructor

Expected Behavior:

It should be possible to provide independent XML documentation comment for class data type even when primary constructor is used.

Actual Behavior:

The constructor XML documentation is displayed when the class data type is being hovered above:

[wsugarman]

This is honestly the only reason I do not use primary constructors for public types.

[LWChris]

One could image something like this:

/// <summary>A</summary>
public record Foo
{
    /// <summary>B</summary>
    /// <param name="bar">C</param>
    public Foo(object bar)
    {
        Bar = bar;
    }

    /// <summary>D</summary>
    public object Bar { get; init; }
}

/// <summary>A</summary>
/// <ctor>
///   <summary>B</summary>
///   <param name="Bar">C</param>
/// </ctor>
/// <member name="Bar">
///    <summary>D</summary>
/// </member>
public record Foo(object Bar)
{ }

• It requires creation of only two new tags: ctor and member
• IntelliSense support of member[name] is equivalent to param[name] of the primary constructor
• The benefit of enclosing tags is
  • On the implementing side: all existing XML documentation (summary, remarks, example, exception, seealso, ...) can remain as-is, without the need to invent new tags or referencing/mapping mechanisms.
  • On the refactoring side: you can simply wrap the existing XML documentation inside the respective enclosing tags, without the need to reformat anything

All this should make implementing the parser, the IntelliSense, the QuickFix refactoring, and manual refactoring super easy while maintaining full feature compatibility with current and future additions.