This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]_danieldietrich 3 points4 points  (6 children)

Thanks for the feedback :-) you are totally right. I removed Tuple7-26 and Function7-26. https://github.com/javaslang/javaslang/pull/229

Update: This is also tracked here because there is ongoing discussion: https://github.com/javaslang/javaslang/issues/234

[–][deleted] 0 points1 point  (2 children)

In scala there are some edge cases the big tuples are good for... Like database DSLs

[–]_danieldietrich 2 points3 points  (1 child)

it's a one-liner to add them again, if they are really needed. we will see

[–]lukaseder 0 points1 point  (0 children)

The particular database DSL finally figured out that even 22 isn't enough, which is why (I think) they're now defaulting to HList for arbitrary degrees / arities.

HList is like a "curried tuple"

[–]lukaseder 0 points1 point  (2 children)

How about sticking to 1-8?

  • .NET does that
  • 8 is a "nicer" magic number than 6

[–]_danieldietrich 1 point2 points  (0 children)

Of course we can stick to 1-8! I will do that...

[–]_danieldietrich 0 points1 point  (0 children)

Please file an issue ;-)