-
Notifications
You must be signed in to change notification settings - Fork 21
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
The 8-year-old problem: Fully qualified name, unqualified name with import declaration resolve differently #809
Comments
I'm not sure about back in 2012,but I currently resolve such conflicts simply by using It's also in the docs:
Though I think the ambiguities between using (I'm not saying this behaviour shouldn't be fixed, just that there's a non ambiguous way around it, specifically designed for this case) |
Just to note that the issue as-written in SO and this suggestion doesn't reproduce on .NET Core:
Given that I don't think it's likely we'd do this just for .NET Framework, though we'd probably accept a PR that implements it correctly. |
Not just .NET Framework, developing libraries on .NET Standard has this issue too. |
I think this is only true if you're using the desktop compiler. This equally does not reproduce on .NET Core on unix for .NET Standard. We're intending to replace the desktop compiler entirely, so I don't think this is a language suggestion that'll be implemented. |
Closing out this old issue |
https://stackoverflow.com/questions/8732769/fully-qualified-name-unqualified-name-with-import-declaration-resolve-different
I propose we allow fully qualified names to resolve to the nongeneric overload when multiple overloads of different arity are present. (The first entry of the following should be valid.)
The existing ways of approaching this problem in F# are the last three entries.
Pros and Cons
The advantages of making this adjustment to F# are
The disadvantages of making this adjustment to F# are none that I can think of.
Extra information
Estimated cost (XS, S, M, L, XL, XXL): XS - Related implementation information can be found in the linked StackOverflow question.
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply:
The text was updated successfully, but these errors were encountered: