-
Notifications
You must be signed in to change notification settings - Fork 1.1k
check whether a value class parameter is call-by-name #5176
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, and thank you for opening this PR! 🎉
All contributors have signed the CLA, thank you! ❤️
Have an awesome day! ☀️
@@ -1666,6 +1666,13 @@ object messages { | |||
val explanation = "" | |||
} | |||
|
|||
case class ValueClassParameterMayNotBeCallByName(valueClass: Symbol, param: Symbol)(implicit ctx: Context) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should reuse VarValParametersMayNotBeCallByName
instead and maybe addapt a bit it's explanation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was my first idea, but I thought it might be confusing, because it's not really a val
and doesn't seem to behave like a case class parameter, which implicitly is a val
, either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right
@nicolasstucki I don't think we should forbid this. We should fix the infinite loop of course |
@Jasper-M then could you just change the commit message to be |
Thanks @Jasper-M |
Thanks @Jasper-M, and nice to see you here! |
fixes #5121