Post

Christophe B.
@bladecoder.bsky.social

A lot of things changed since #Kotlin 1.1, for example starting with Kotlin 1.5 the compiler is optimizing for loops of any combination of functions creating an integer progression. Check out the very unreasonable example near the end of this revised post: dev.to/cbeyls/explo...

dev.toExploring Kotlin’s hidden costs — Part 3: Delegated properties and rangesFollowing the overwhelming positive feedback I received after publishing the first two parts of this...

0 reposts1 like

Romain Guy
@romainguy.dev

The overhead of companion objects is worse than it seems when you drop down to the arm assembly. When accessing non constants, having to access the insurance means doing an initialization check at each call site.

Christophe B.
@bladecoder.bsky.social

You mean when accessing fields of Companion objects from the main class? I assume there is still some overhead yes but I didn't investigate. I also assume R8 improves things on Android by using staticization.