We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
Currently, case classes can't venture past 22 parameters, because they the companion class of can't find suitable FunctionN and TupleN instances for the apply/unapply methods.
But these are arguably the least important features of case classes, and we can make all the others (including pattern matching) work perfectly without them.
There was some understandable fear of the piecemeal when I tabled this on scala-internals (https://groups.google.com/forum/#!topic/scala-internals/RRu5bppi16Y). But I'm convinced this is an area where we can endeavour to inflict less pain.
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-7296?orig=1
Affected Versions: 2.10.0
Sorry, something went wrong.
No branches or pull requests