[Possibly Missing Specification?] XML-Documentation of "delegate*<>" method parameters #5914
-
Imagine having the following codebase: /* L01 */ static unsafe class C
/* L02 */ {
/* L03 */ static void M<T>(delegate*<T> ptr) { }
/* L04 */
/* L05 */ static void M(delegate*<void> ptr) { }
/* L07 */
/* L08 */ /// <inheritdoc cref="C.M{T}(delegate*{T})"/>
/* L09 */ static void M() { }
/* L10 */ } When trying to compile this code (see here on sharplab.io), I receive the following warnings on line
This error occurs regardless on whether one writes /// <inheritdoc cref="C.M{T}(delegate*{T})"/> or /// <inheritdoc cref="C.M(delegate*{void})"/> This therefore does not seem to be an issue with the generic method type parameters or their usage inside the declaration of the parameter I am now wondering: Is this an issue inside the C# language specs or inside the Roslyn compiler? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I also opened an issue on |
Beta Was this translation helpful? Give feedback.
-
Svick linked you to the duplicate issue: dotnet/roslyn#48363. To be frank, yes this is on my plate, but you are precisely the third person to ask for this in nearly as many years. It just hasn't risen to the top of my priority list, and requires coordination with a few other teams to define it as we need to encode new concepts that can't be expressed currently. |
Beta Was this translation helpful? Give feedback.
Svick linked you to the duplicate issue: dotnet/roslyn#48363. To be frank, yes this is on my plate, but you are precisely the third person to ask for this in nearly as many years. It just hasn't risen to the top of my priority list, and requires coordination with a few other teams to define it as we need to encode new concepts that can't be expressed currently.