Proposal to improve Arrow.pdf

# arrow-contributors

[Rachel]

Proposal to improve Arrow.pdf

Proposal to improve Arrow.pdf

[simon.vergauwen]

Is there any impact on MPP?
Can we take any measures to prepare for MPP here already? I am unsure what it involves, and how much our current Gradle config is coupled to java specific tasks.

[simon.vergauwen]

cc\ @thanerian just saw your message in the other thread

[Rachel]

I don't know if I understand the concern properly 🙏 though artifacts, repositories and necessary dependencies will remain the same. In summary, we just reorganize the content. I don't know if I answered the concern about the use of Arrow from multiplatform projects 😅

[simon.vergauwen]

I haven’t worked with MPP yet, but it requires splitting further up in modules or is that just src folders 🤔 similar to Android module product/flavors

[Rachel]

Just src directories:

[Rachel]

https://kotlinlang.org/docs/tutorials/mpp/multiplatform-library.html

[Rachel]

For example, serialization library:

[Rachel]

https://github.com/Kotlin/kotlinx.serialization/tree/master/runtime

[Rachel]

And change the Gradle configuration

[Rachel]

I think that adaptation can be done easily if we split the repository, because the use of plugins is the only thing that cannot be shared from just a repository

[Rachel]

I've looked at it, because someone is asking for it in #arrow channel

[stojan]

I would say not all of them should share the same config. The benchmarks project is a good example. When I did the PR to update to gradle 6 for Arrow, I had to update a bunch of plug-ins related to arrow benchmarks.

Arrow and arrow benchmarks could be built with different gradle versions without a problem

[simon.vergauwen]

Yes, but when Arrow Fx lands 1.0 we’d probably want to run benchmarks on every PR in Arrow Fx. It’s to benchmark IO and prevent regression in perf.