-
Notifications
You must be signed in to change notification settings - Fork 32
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
Wrongly converts classes with multiple constructors #73
Comments
Sorry, this kind of delegation is the best that can be done. |
What about something like this? It does not look very nice but at least it's behavior equivalent:
|
Hm, this is an interesting approach, I will consider it. |
@OlivierBlanvillain: why is the current behavior wrong? the default constructor shouldn't be declared explicitly in Scala... I would be very disappointed if Scala wrapped the default constructor in a |
I think the point is that if the behaviour can't be solved with constructor delegation then a common delegation target could be used. This is again a tradeoff between correctness of the result vs having a scalaesque result. |
Here is an example:
Which is converted to:
Note that it might be impossible to perfectly match Java behavior, especially when inheritance is involved, see http://stackoverflow.com/questions/3299776/in-scala-how-can-i-subclass-a-java-class-with-multiple-constructors.
The text was updated successfully, but these errors were encountered: