how does one handle situations for zipOrAccumulate...
# arrow
u
how does one handle situations for zipOrAccumulate that require more than 9 actions ?
a
you nest several zipOrAccumulate, each of them returning a subset of the actions
k
You can use one of the variants in the arrow-core-high-arity module.
u
thanks guys. I have decided to use the high arity module, but when building I get weird errors such as:
Unresolved reference 'nel'
,
Unresolved reference 'bindAll'
,
Unresolved reference 'either'
, and other similar errors.
Copy code
Duplicate class arrow.core.IterableKt found in modules arrow-core-high-arity-jvm-1.2.4.jar -> arrow-core-high-arity-jvm-1.2.4 (io.arrow-kt:arrow-core-high-arity-jvm:1.2.4) and arrow-core-jvm-1.2.4.jar -> arrow-core-jvm-1.2.4 (io.arrow-kt:arrow-core-jvm:1.2.4)
     Duplicate class arrow.core.MapKt found in modules arrow-core-high-arity-jvm-1.2.4.jar -> arrow-core-high-arity-jvm-1.2.4 (io.arrow-kt:arrow-core-high-arity-jvm:1.2.4) and arrow-core-jvm-1.2.4.jar -> arrow-core-jvm-1.2.4 (io.arrow-kt:arrow-core-jvm:1.2.4)
My gradle build file looks like:
Copy code
implementation('io.arrow-kt:arrow-fx-coroutines:1.2.4')
implementation('io.arrow-kt:arrow-core-high-arity:1.2.4')
implementation("io.arrow-kt:arrow-core-jvm:1.2.4")
a
can you report an issue? this may be the same problem we had with
optics-compose
some time ago
k
@Alejandro Serrano.Mena what as the solution to
optics-compose
? Would like to try my hand when I find time to figure out a solution for this as I need the
high-arity
variants.
a
we had to change the name in the code itself, because otherwise the compiler complains
k
thanks, noted