Kotlin tricks: Non-exhaustive enums
Enums are an exhaustive set of values. But what if you suspect you may want to add new entries in the future?
Enums are an exhaustive set of values. But what if you suspect you may want to add new entries in the future?
The most common way of measuring elapsed time is flawed.
There are so many kinds of parameters! Is there an order in which they should be declared?
The Arrow library is quite poorly known. As Kotlin 2.4.0 is around the corner, bringing stable context parameters, it is time to brush a few misconceptions.
Did you know there are a few different ways to make Kotlin varargs mandatory?
To understand discussions about Gradle, it's necessary to understand how things are named—and that can be quite confusing.