Uploaded April 2026 | Updated September 2026, 2 weeks ago
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
In most imperative languages, you can 'return' from any point in the body of the function. The same applies for 'break'ing and 'continue'ing a loop. But what if you could do so across functions? This is allowed in Kotlin with 'inline' functions!
In this talk we describe how the 'inline' function mechanism in Kotlin works. This means that we're no longer tied to a handful of language constructs for early returning: a 'forEach' function becomes indistinguishable from a 'for' loop. Several design patterns related to stopping early are no longer needed, leading to much simpler code to write and read.
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
In most imperative languages, you can 'return' from any point in the body of the function. The same applies for 'break'ing and 'continue'ing a loop. But what if you could do so across functions? This is allowed in Kotlin with 'inline' functions!
In this talk we describe how the 'inline' function mechanism in Kotlin works. This means that we're no longer tied to a handful of language constructs for early returning: a 'forEach' function becomes indistinguishable from a 'for' loop. Several design patterns related to stopping early are no longer needed, leading to much simpler code to write and read.
