Which modules do you want to transform to a MPP pr...

# arrow-contributors

[addamsson]

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)

[addamsson]

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)

[addamsson]

I just bumped into this problem when I was porting the exact same class from VAVR (PartialFunction)

[addamsson]

kind of a funny coincidence

[addamsson]

one solution for this is to define `Function*`s in a way that it doesn't have operator fun invoke

[simon.vergauwen]

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.

[addamsson]

I'm going to open an issue for this in Kotlin

[addamsson]

the exception says that extending function interfaces is not supported in the Javascript target

[simon.vergauwen]

All that tells us is that the compiler doesn't support it 🤷‍♂️

[addamsson]

maybe they'll fix it

[addamsson]

but it blocks MPP right now 😞

[addamsson]

@simon.vergauwen so theoretically I can inline all the boilerplate which is generated by @higherkind and @extension, right?

[addamsson]

apart from KindedJ's stuff

[simon.vergauwen]

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

[addamsson]

great!