Skip to content

Avoid nonsensical error message in processByNameArgs #7830

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
Dec 22, 2019

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Dec 21, 2019

Transforming the argument can already cause errors coming from
TypeAssigner that need to be caught instead of being issued.

Transforming the argument can already cause errors coming from
TypeAssigne rthat need to be caught instead of being issued.
The previous code was buggy in that *all* arguments of a method
containing a single by-name argument were post processed.
@odersky odersky requested a review from abeln December 21, 2019 17:32
@@ -0,0 +1,8 @@
-- Error: tests/neg-custom-args/explicit-nulls/byname-nullables1.scala:10:6 --------------------------------------------
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding a test that uses the byName method referred to here.

@odersky odersky merged commit 77ec689 into scala:master Dec 22, 2019
@odersky odersky deleted the fix-flow branch December 22, 2019 13:20
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.

2 participants