Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use an Attribute to specify overload resolution priority #821

Open
gusty opened this issue Dec 17, 2019 · 0 comments
Open

Use an Attribute to specify overload resolution priority #821

gusty opened this issue Dec 17, 2019 · 0 comments

Comments

@gusty
Copy link

@gusty gusty commented Dec 17, 2019

Use an Attribute to specify overload resolution priority

I propose we add a way to use an Attribute to specify overload resolution priority

The existing way of approaching this problem in F# is adding a "marker" dummy parameter with a concrete class which inherit from other objects which will be used to mark less priority, since the overload resolution prefers the type which is closer in hierarchy.

This will be very valuable when using member constraints, projects like F#+ or the Task Builder, including the upcoming version baked into the compiler, make use of this workaround due to lack of a formal mechanism.

Pros and Cons

The advantages of making this adjustment to F# are:

  • More control over overload resolution.
  • Less cases leading to ambiguity resolution compile-time errors

The disadvantages of making this adjustment to F# are:

  • Adding an extra modifier attribute

Extra information

Estimated cost: S:

Related suggestions: #819 #820

Affidavit (please submit!)

Please tick this by placing a cross in the box:

  • This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
  • I have searched both open and closed suggestions on this site and believe this is not a duplicate
  • 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:

  • This is not a breaking change to the F# language design
  • I or my company would be willing to help implement and/or test this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.