We have a stacktrace in which the Kotlin line numb...
# announcements
j
We have a stacktrace in which the Kotlin line number given is after the end of the file. This post (discuss.kotlinlang.org/t/stacktrace-points-to-line-after-end-of-file/4129/2) indicates that this is a consequence of a compiler workaround for inlined code fragments. Given that class has numerous lengthy
.foreach{}
inlines blocks , this leaves us with a problem in tracking down the issue. Is there any way to get additional information as to where the actual issue is?