@raulraja it's https://github.com/arrow-kt/arrow/pull/690. The commit is https://github.com/arrow-kt/arrow/pull/690/commits/0206036779434c1ecb8fdc803dffb1e635d74945. Thx!

the section

Documentation, with tests

is interesting

if we could do something similar with Ank

not only process markdown files but code inside KDocs

I think there is already issue for that

cool 😄

Working on

@arities(fromTupleN = 2, toTupleN = 22 | fromHListN = 1, toHListN = 22)

which will allow users of arrow expand on their project the instances possible for Tuples and HList such as that data classes that are isomorphic to those can have automatic generic derivation of Monoid, Eq, Hash, Order, etc...

We'll be able to do things like:

@generic(deriving = [Semigroup::class])
data class Item(val weight: Int)

val newItem = Item(100) + Item(100) // or Item(100).combine(Item(100))
//Item(200)

with the Semigroup HList and Tuple instances...

We can also use the generic derivation to build better pattern matching instrospecting the data classes properties to reify them and adapt them to partial functions similar to how Scala does pattern matching which is slightly more powerful than Kotlin's

when

thanks to

unapply

and Extractors.

Proposal: rename pure to just

It's less canonical, more intuitive

It shares name with Rx and reads better on documentation for new users

I'm fine either way and if

just

is more familiar to Kotlin users then I think it'd be a good change but before we do that we should probably review all combinator names in all type classes to do all at once. The times where we can introduce these changes easily is coming to an end as we approach 1.0

👍

also, remember to deprecate, not just delete. We have more users now

so version 0.7.X is going to come with a bunch of changes

in february we had the renamening, which is going to break everyone

so we’re going to use this opportunity to clean house in another aspect: syntax

we’ll remove the old syntax that uses the global lookup code

it’s proven that it won’t scale or work without external tooling like dagger

or encoding things using

typeclasseless

style

so it’s going to go out

and with it, some of the magic code

I’ll change

pure

to

just

too, hope it doesn’t break way too many people

it’ll be a jump in QoL equivalent to the merge with funKtionale

Lookup methods will stay, right?

no

Oh, that will break quite some stuff I think.