In this talk I present a pragmatic approach for porting Java Libraries to Kotlin without leaking platform types into the public API through a interesting case study.
Platform types destroy some of the wonderful safety guarantees that Kotlin provides. They're a necessary evil to provide nice interop with Java, but that doesn't mean we have to allow them to propogate throughout our code base.
The example we'll look at is creating a Kotlin version of the wonderful Github Scientist library. Recently, I was trying to PoC something out for a team to illustrate how Github Scientist's interesting approach to data-driven refactoring could be applied in Kotlin. Unfortunately, there wasn't a Kotlin version of Github Scientist available, so I had to create one :).