Book Image

Functional Kotlin

Book Image

Functional Kotlin

Overview of this book

Functional programming makes your application faster, improves performance, and increases your productivity. Kotlin supports many of the popular and advanced functional features of functional languages. This book will cover the A-Z of functional programming in Kotlin. This book bridges the language gap for Kotlin developers by showing you how to create and consume functional constructs in Kotlin. We also bridge the domain gap by showing how functional constructs can be applied in business scenarios. We’ll take you through lambdas, pattern matching, immutability, and help you develop a deep understanding of the concepts and practices of functional programming. If you want learn to address problems using Recursion, Koltin has support for it as well. You’ll also learn how to use the funKtionale library to perform currying and lazy programming and more. Finally, you’ll learn functional design patterns and techniques that will make you a better programmer.By the end of the book, you will be more confident in your functional programming skills and will be able to apply them while programming in Kotlin.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Single-expression functions


Until now, all our examples were declared in a normal way.

The function sum takes two Int values and adds them. Declared in a normal way, we must provide a body with curly braces and an explicit return:

fun sum(a:Int, b:Int): Int {
   return a + b
}

Our sum function has its body declared inside curly braces with a return clause. But if our function is just one expression, it could have been written in a single line:

fun sum(a:Int, b:Int): Int = a + b

So, no curly braces, no return clause, and an equals (=) symbol. If you pay attention, it just looks similar to a lambda. 

If you want to cut even more characters, you can use type inference too:

fun sum(a:Int, b:Int) = a + b

Note

Use type inference for a function's return when it is very evident which type you are trying to return. A good rule of thumb is to use it for simple types such as numeric values, Boolean, string, and simple data class constructors. Anything more complicated, especially if the function does any transformation...