So, regarding <this> There are several options, I’m interested on knowing what you all think :slight...

# arrow-contributors

[pablisco]

So, regarding this There are several options, I’m interested on knowing what you all think 🙂
1️⃣ Create a new repository called arrow-extras and create a module called arrow-smash
2️⃣ Create a sole repository called arrow-smash with Can, Smash and Wedge from this hackage
3️⃣ Create a module inside arrow-core called arrow-core-extras (to be moved along to arrow-datatypes when we untangle arrow-core
4️⃣ Something completely different (please comment)
Thank you all

[raulraja]

I think 1 as @Jannis mentioned in the issue is a reasonable path because right now we need to keep things out of core to proceed with the 0.11 and 1.0 release. We are mostly pruning and not adding things.

[pablisco]

Yeah, totally agree. Smaller modules/repos is the way forward. Specially if we build/test things independently. That's why I was asking to see what people think. For me 2️⃣ seems like the most flexible one of the options as it doesn't influence other modules. Also, if we move to independent versioning then this can have its own lifecycle

[raulraja]

Instead of independent versioning we need to release with the language since meta will be coupled to the unstable compiler until it becomes more stable. That is you will be able to use the KOTLIN_VERSION for all arrow modules. As for this module arrow-extras should live in the incubator until we decide how to promote the data-types if they are useful and potentially extract it as you said but decoupled from MTL. It's fine to also call it smash if it's in the incubator repo

[pablisco]

Aright, I’ll move it to arrow-smash inside the incubator for now 🙂

https://24.media.tumblr.com/7299bb2cf2b72277f0636ec2d4f7866f/tumblr_mr97dnvI8j1sewcjpo1_400.gif▾

[pablisco]

cc: @pakoito 🧌

[pablisco]

Moved in this other PR:
https://github.com/arrow-kt/arrow-incubator/pull/127