-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
defining the choice of overload when more than one applies #8
Comments
Yes, the desired behaviour is to pick the first matching overload variant. It should be described in the documentation. |
Ah, and the type checker should probably give a warning in cases like the above example, since the second overload can never be called. |
By the way, the overview page says:
|
Oops, that's how I initially designed it, but it turned out to be a bad idea (often there is no single most specific signature). No it should be fixed in the overview. |
Yeah, I agree that first match is a better idea, just wanted to point out the discrepancy in the docs. |
I don't think it's completely clear what the following example should print:
One might intuitively expect the 'best match' to be chosen, which would print 'B', but the current implementation actually chooses the 'first match', which would print 'A'. This isn't wrong per se but I think it's at least worth documenting.
The text was updated successfully, but these errors were encountered: