4 ms·
You can write two-way interop -- I didn't mean to suggest otherwise. But there are Kotlin features that don't map like type-safe @Dsl's which puts you in a pos
by danneu 9y ago
You can write two-way interop -- I didn't mean to suggest otherwise.
But there are Kotlin features that don't map like type-safe @Dsl's which puts you in a position where you have to make concessions for interop.
- edem 9y agoNow that is true. You also can't use reified generics (which is a bit hacky anyway).
- PopsiclePete 9y ago"It totally works...except for A, B....oh yeah and C, but C kinda sucks....well D is awful too, you should never use D...." So basically, he was right, and you weren't. There is no seamless 2-way interop, yes?
- hibbelig 9y agoI don't understand this sentiment. I understand Kotlin has more features than Java, and of course it's tough to call the advanced things from Java. At least so I would think.
- edem 9y agoNo he was not right. You can write two-way interop and it is not hard. I have actually written a library which does it. He did not say that "the two-way interop is not seamless". He said that you "can't write two way interop code" which is not true.