This feature is beneficial for projects defining custom source sets, since the compilation of independent source sets can be parallelized. In the case of multiplatform projects, targets for different platforms can also be built in parallel. For Android, the debug and release build types can be compiled in parallel.

This sounds pretty cool, however I paused to think how often would i need the debug and release build types to be compiled in parallel? Probably CI like environment? oooo but with androidTest and test ? that might help.

Brings improvements for inline classes

inline classes imho, is one of those things developers should jump on to right away. It can have a significant impact on the way you do development especially as it relates to Type driven design. I did a fragmented episode on the subject recently.

All improvements to inline classes, highly welcome 🙏.

Since Kotlin 1.3, you can use the main function without parameters.

For the kscripters, this is actually pretty nifty. I missed the introduction of this feature in 1.3.

A new intention allows to convert constructs using lambdas with SAM to anonymous objects.

If you understand this well, you’ll realize this almost seems backwards. Why would i ever want SAM -> anonymous you ask? Hello dear RxJava Kotlin users, read this blog post on Kotlin’s SAM problem to understand the specifics better.

In addition, we’ve added support for Compile Avoidance for kaptKotlin tasks in Gradle, improving build performance times.

I hate on kapt a lot for affecting my build times. Any improvement here is always welcome.

In closing, how cool is it, my chosen programming language gets an update, and i can start using it almost right away? (let the Java-writing-old-timers from the early Android world envy).


Permalink