You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VS tooltip display too verbose when calling overloaded method with wrong parameter types #6578
A unique overload for method 'Run' could not be determined based on type information prior to this program point. A type annotation may be needed. Candidates: Task.Run<'TResult>(function: Func<'TResult>) : Task<'TResult>, Task.Run<'TResult>(function: Func<Task<'TResult>>) : Task<'TResult>
It doesn't look great in VS:
Looking for:
A unique overload for method 'Run' could not be determined based on type information prior to this program point.
A type annotation may be needed.
Candidates:
- Task.Run<'TResult>(function: Func<'TResult>) : Task<'TResult>
- Task.Run<'TResult>(function: Func<Task<'TResult>>) : Task<'TResult>
Please let me know if that makes sense.
I've made some progress in my branch (#6596) for the initial case:
There is work ahead for additional coverage of those messages as it is only lightly covered in fsharpqa tests. (edit: coverage seems appropriate)
More input from users with verbose overload resolution messages in advanced and simple cases would be greatly appreciated.
Activity
smoothdeveloper commentedon Apr 20, 2019
Relevant locations:
https://github.com/Microsoft/visualfsharp/blob/c4c1d9cf1097955a71c7cbc328a6b5c672a34bda/src/fsharp/ConstraintSolver.fs#L2379-L2399
https://github.com/Microsoft/visualfsharp/blob/c4c1d9cf1097955a71c7cbc328a6b5c672a34bda/src/fsharp/TypeChecker.fs#L9877-L9944
https://github.com/Microsoft/visualfsharp/blob/c4c1d9cf1097955a71c7cbc328a6b5c672a34bda/src/fsharp/CompileOps.fs#L765-L770
https://github.com/Microsoft/visualfsharp/blob/c4c1d9cf1097955a71c7cbc328a6b5c672a34bda/src/fsharp/FSStrings.resx#L162-L164
smoothdeveloper commentedon Apr 25, 2019
I'll look at this message (sample from #2503 (comment)):
Actual:
It doesn't look great in VS:
Looking for:
Please let me know if that makes sense.
I've made some progress in my branch (#6596) for the initial case:
There is work ahead for additional coverage of those messages as it is only lightly covered in fsharpqa tests. (edit: coverage seems appropriate)
More input from users with verbose overload resolution messages in advanced and simple cases would be greatly appreciated.
smoothdeveloper commentedon Nov 29, 2020
closing this one which got merged in #6596.