Skip to content

Document different handling of default arguments in overloading #14775

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

Merged
merged 2 commits into from
Mar 25, 2022

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Mar 25, 2022

Document different handling of default arguments in overloading
resolution relative to Scala-2.

Fixes #14765

Document different handling of default arguments in overloading
resolution relative to Scala-2.

Fixes scala#14675
Copy link
Contributor

@som-snytt som-snytt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change better reflects the principle that overload resolution is guided by the definitions and not "what the user wrote".

This is the micro-SIP process at work, SIP = Scala Implementation Preferred.

@odersky odersky requested a review from smarter March 25, 2022 18:43
@smarter smarter enabled auto-merge March 25, 2022 18:47
@smarter smarter merged commit 6f3fe05 into scala:main Mar 25, 2022
@smarter smarter deleted the fix-14675 branch March 25, 2022 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Behavior of overloaded varargs and default parameter value differs from Scala 2
3 participants