Champion "CallerArgumentExpression" is currently in the C# team's working set.
I propose we support this attribute, which has been present since .NET Core 3.0. We can match this attribute by namespace so that it can be defined even when outside .NET Core.
The motivation, pros, and cons can be seen in the C# proposal. To summarize, this allows developers to capture the expressions passed to a method, to enable better error messages in diagnostic/testing APIs and reduce keystrokes.
Extra information
Estimated cost (XS, S, M, L, XL, XXL): M
Related suggestions: #463 - F# compiler should support CallerLineNumber, CallerFilePath etc (Completed for F# 4.1)
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply:
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.
Champion "CallerArgumentExpression" is currently in the C# team's working set.
I propose we support this attribute, which has been present since .NET Core 3.0. We can match this attribute by namespace so that it can be defined even when outside .NET Core.
The motivation, pros, and cons can be seen in the C# proposal. To summarize, this allows developers to capture the expressions passed to a method, to enable better error messages in diagnostic/testing APIs and reduce keystrokes.
Extra information
Estimated cost (XS, S, M, L, XL, XXL): M
Related suggestions: #463 - F# compiler should support CallerLineNumber, CallerFilePath etc (Completed for F# 4.1)
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply:
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.