Question: the JVM team are currently rewriting how...
# announcements
m
Question: the JVM team are currently rewriting how stack traces work. There's a new API for generating them efficiently and the Throwable.printStackTrace() code is being modified to use it. I wonder if this would be a good time for the Kotlin guys to petition the HotSpot guys to use the extra debug info that's in the class files, so stack traces that have inlined functions work better without the hacks currently needed?