Kotlin 1.7.0 introduces build reports that help track compiler performance. Reports contain the durations of different compilation phases and reasons why compilation couldn't be incremental. Build reports toString() 1.55s 1.546s Duration.milliseconds(25.12).toString() 25.1ms 25.12ms The way negative durations are represented has also been changed. A negative duration is prefixed with a minus sign (-), and in YouTrack. 245 it is surrounded with parentheses: -12m and -(1h 30m). Note that small durations of less than one second are represented as a single number with one of the subsecond units. For

Kotlin 1.7.0 introduces build reports that help track compiler performance. Reports contain the durations of different compilation phases and reasons why compilation couldn't be incremental. Build reports 1.55s 1.546s Duration.milliseconds(25.12).toString() 25.1ms 25.12ms The way negative durations are represented has also been changed. A negative duration is prefixed with a minus sign ( - ) multiple components, it is surrounded with parentheses: -12m and -(1h 30m) . Note that small durations of less than one second are represented as a single number with one of the subsecond units. For

Kotlin 1.7.0 introduces build reports that help track compiler performance. Reports contain the durations of different compilation phases and reasons why compilation couldn't be incremental. Build reports 1.55s 1.546s Duration.milliseconds(25.12).toString() 25.1ms 25.12ms The way negative durations are represented has also been changed. A negative duration is prefixed with a minus sign ( - ) multiple components, it is surrounded with parentheses: -12m and -(1h 30m) . Note that small durations of less than one second are represented as a single number with one of the subsecond units. For