Fix the arity limitations/implementation restrictions of tuples, functions, case classes

[scabug]

This issue seems to come up every second week. This becomes more pressing as people play with various kinds of code generation or adopt Slick (and have more than 22 database columns).

There doesn't seem to be an agreement yet on how to handle this, but now there is at least a ticket.

Selection of older discussions:
https://groups.google.com/d/topic/scala-internals/RRu5bppi16Y/discussion
https://groups.google.com/d/topic/scalaquery/qjNW8P7VQJ8/discussion
https://groups.google.com/d/topic/scalaquery/qmg5Lj3io9Y/discussion
https://groups.google.com/d/topic/scala-language/YxljyAYVzA0/discussion
...

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-7099?orig=1
Reporter: @soc
Affected Versions: 2.9.2, 2.10.0, 2.11.0-M1

[scabug]

Vladimir Nicolici (vladnc-at-gmail.com) said:
Another ORM affected by the 22 limit is scala-activerecord: aselab/scala-activerecord#27

Also mentioned in that issue is the play framework JSON inception.

[scabug]

Lev Brailovskiy (lev4ik) said:
When this issue is planed to be solved?

[scabug]

Leonard Schneider (leonard.schneider) said:
Case classes has been fixed in #7098 from Scala 2.11.0.