Any thoughts if I should open this issue as a Kotlin bug or kotlinlang #announcements

Any thoughts if I should open this issue as a Kotl...

jlleitschuh

08/31/2017, 5:15 PM

Any thoughts if I should open this issue as a Kotlin bug or a JVM bug? And any suggestions on how to go about working around the issue?