https://kotlinlang.org logo
#arrow-contributors
Title
# arrow-contributors
a

addamsson

07/17/2019, 8:22 AM
Which modules do you want to transform to a MPP project first? I've identified some modules which use some features which won't work in Javascript targets because they inherit from functions (which is not supported by the JS target)
Some of these are in one of the
core
modules like
Bifunctor
,
AndThen
and
PartialFunction
(although this will be deprecated, I've read the issue)
I just bumped into this problem when I was porting the exact same class from VAVR (
PartialFunction
)
kind of a funny coincidence
one solution for this is to define `Function*`s in a way that it doesn't have
operator fun invoke
s

simon.vergauwen

07/17/2019, 8:25 AM
Core has the be first, since all others depend on it. But I guess we should move some stuff like
AndThen
to a JVM module because it exists for stack safety reasons. It's very cumbersome... Curious why this limitation.
a

addamsson

07/17/2019, 8:25 AM
I'm going to open an issue for this in Kotlin
the exception says that extending function interfaces is not supported in the Javascript target
s

simon.vergauwen

07/17/2019, 8:26 AM
All that tells us is that the compiler doesn't support it 🤷‍♂️
a

addamsson

07/17/2019, 8:27 AM
maybe they'll fix it
but it blocks MPP right now 😞
@simon.vergauwen so theoretically I can inline all the boilerplate which is generated by
@higherkind
and
@extension
, right?
apart from KindedJ's stuff
s

simon.vergauwen

07/17/2019, 8:38 AM
Jep absolutely but I'd skip the
@extension
stuff for now. We're going to replace that soon anyway and it's only user facing
a

addamsson

07/17/2019, 11:00 AM
great!
2 Views