Once upon a time, there were two gangs in the wild west: Swift and Kotlin. Both being equally strong but in different ways. One day, a guy in the Kotlin gang discovered that the Swift gang was able to carry out operations that the Kotlin guys could only dream of. And so he looked into the sky and said to the Kotlin gang: “My fellow cowboys and cowgirls: the Swift gang has something that we are clearly missing. I have a proposal today. I see a way how, one day, we will be able to do something equally awesome as they do now!”. And so KEEP-87 was born, a proposal for a new Kotlin language feature.
There are many cases when execution context of a code is important. In server-side programs context may carry diagnostic information; in UI applications widgets can only be touched from the specific main thread. This may create a potential problem when your code becomes larger, especially when you decouple data producers and data consumers. Kotlin Flows are designed to enable such modularization, so let us see how they behave with respect to an execution context.
In this post I am going to show you how to solve a common problem that arises when using dynamic feature modules in your project: code defined inside them is inaccessible to your base application during compilation… unless you use reflection 😱.
In this episode, Donn talks to Matt Runo about the Flank project. Using Flank you can run your Espresso test suite in parallel on Firebase Test Lab (FTL). This allows you to lower your feedback loop time and increase developer productivity and throughput. You’ll learn all about Flank, how it works and how to get started in this episode.