You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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: