Tuple first

[Jolanrensen]

Implements some version of my old library: https://github.com/Jolanrensen/ScalaTuplesInKotlin/tree/main

There is some speed loss when working with functions that prefer Arities and Pairs over Tuples since those are what Spark is optimized for. Putting Tuples first will thus probably lower the confusion of users and increase performance :)

Sort of follow up from #76

[Jolanrensen]

Maybe takeN(), dropN() (and takeLastN(), dropLastN()) and splitAsN() could also be added, since they are added in Scala 3, similar to zip.
map {} might also be a simple one.

Not sure if this is becoming overkill or still useful XD

[asm0dey]

LGTM, but I cant say that I've carefully reviews everything generated

[Jolanrensen]

LGTM, but I cant say that I've carefully reviews everything generated

I'll just check how performance of IntelliJ is while working on something else when having these tuples present in the project. If that's fine I'll merge it :)

[asm0dey]

Nice plan!

[Jolanrensen]

Performance is way better in a separate module :) tried it with the streaming functions. Consecutive builds are way faster than full ones. The only downside is that now dokka won't include the tuples. We could publish it to a separate docs branch while we haven't switched to gradle yet? I thought gradle did support multi-module dokka