Re:Scala turns 10
by thescrewdriver on Monday January 20, 2014 @10:30AM
(#7089945)
I think the only place I've seen anyone wanting more than 22 parameters was people who had a database table with more than 22 rows (!) and where using the SLICK library.
[ Parent
| on HN ]
Yeah we ran into this problem... Scala and the whole ecosystem can get annoying. In the real world, outside of the academic bubble that Scala lives in, database tables are over 22 columns.
In Scala I find it more natural to group multiple columns together / break the case-class representing the table into multiple case-classes. The problem is that Slick needs to serialize/deserialize those case-classes into tuples.
Re:Scala turns 10
by frowaway001 on Tuesday January 21, 2014 @05:04PM
(#7098861)
I think the arity limit is more or less planned to be fixed in Scala > 2.11 anyway.
Re:Scala turns 10
by thescrewdriver on Wednesday January 22, 2014 @04:43AM
(#7101712)
Seems to be fixed in v2.0: http://slick.typesafe.com/news/2014/01/21/slick-2.0.0-releas...
You can also run into it with forms in play, although for a variety of reasons you hit it at 18.
The whole situation just drips with arrogance... "we have a magic number, and if you hit it, you suck"
I agree. I know people posted a comment saying its fixed in 2.11 but if Scala wants to be production ready language it shouldn't take 10 years to address this.
Re:Scala turns 10
by frowaway001 on Wednesday January 22, 2014 @02:45PM
(#7104887)
> "we have a magic number, and if you hit it, you suck"
You mean like Java does since ... forever?