News for hackers. Stuff that matters.
Re:Clojure vs. Scala by lmm on Tuesday December 24, 2013 @11:28AM (#6959977)
Well, that code exists at all for compatibility with tuples, which are a misfeature from the early days of scala. The "right" way to solve the problem is with shapeless' HLists. With HList you could write a simple generic method that would work with a HList of any length. (If you don't need to join a bunch of hetrogenously-typed futures while preserving all their type distinctions then you could just use the method that takes a Seq, above in the file)

(You could also generate exactly this code with macros, which were a new feature in scala 2.10; I imagine a newer version of the code will do that)

Re:Clojure vs. Scala by smrtinsert on Tuesday December 24, 2013 @03:56PM (#6961096)
I'm surprised you can't map over tuple members and join. Should be a one liner, but I'm a scala newbie though. Tupled were an unnecessary choice here.

Pointing to this kind of stuff as an example of scala shows a complete misunderstanding of the language quite honestly.

Re:Clojure vs. Scala by saryant on Tuesday December 24, 2013 @01:10PM (#6960410)
There are some similar ugly workarounds of that nature in Play's JSON macros. Quite ugly but also transparent to anyone not writing library code.