fsharp / fsharp/fslang-suggestions

Consider the return type in overload resolution

Open
#820 21 comments 10 reactions 0 assignees View on GitHub
approved-in-principle area: object-programming
Dominant language
No language data
Stars
373
Forks
21
PR merge metrics
No merged PRs in 30d

Description

I propose we add a mechanism (attribute or language construct) to consider the return type in overload resolution.

The existing way of approaching this problem in F# is to add a dummy parameter with the type of the return type and call the function with its default value.

## Pros and Cons

- More control over overload resolution
- Less cases leading to ambiguity resolution compile-time errors
- Better type inference, since type inference is better when the return type is taken into account.

The disadvantages of making this adjustment to F# are:

- Adding an extra modifier attribute or a language construct.
- It's work.

## Extra information

Estimated cost: S-M

Related suggestions: #819 #821

## Affidavit (please submit!)

Please tick this by placing a cross in the box:
* [x] This is not a question (e.g. like one you might ask on [stackoverflow](http://stackoverflow.com)) and I have searched stackoverflow for discussions of this issue
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate
* [x] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.

Please tick all that apply:
* [x] This is not a breaking change to the F# language design
* [x] I or my company would be willing to help implement and/or test this

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.