Book Image

Kotlin Standard Library Cookbook

By : Samuel Urbanowicz
Book Image

Kotlin Standard Library Cookbook

By: Samuel Urbanowicz

Overview of this book

For developers who prefer a more simplistic approach to coding, Kotlin has emerged as a valuable solution for effective software development. The Kotlin standard library provides vital tools that make day-to-day Kotlin programming easier. This library features core attributes of the language, such as algorithmic problems, design patterns, data processing, and working with files and data streams. With a recipe-based approach, this book features coding solutions that you can readily execute. Through the book, you’ll encounter a variety of interesting topics related to data processing, I/O operations, and collections transformation. You’ll get started by exploring the most effective design patterns in Kotlin and understand how coroutines add new features to JavaScript. As you progress, you'll learn how to implement clean, reusable functions and scalable interfaces containing default implementations. Toward the concluding chapters, you’ll discover recipes on functional programming concepts, such as lambdas, monads, functors, and Kotlin scoping functions, which will help you tackle a range of real-life coding problems. By the end of this book, you'll be equipped with the expertise you need to address a range of challenges that Kotlin developers face by implementing easy-to-follow solutions.
Table of Contents (11 chapters)

Data transformation with map and flatMap

The support for declarative data mapping operations is one of the basic and most powerful features in the functional data-processing domain. Often, when working with data, we need to transform a collection of a specific type into another type. It's also a common scenario to generate a list of objects from each element of a collection and to merge all of those new objects in a target collection together. Those are the use cases where the map() and flatMap() extension functions help.

In this recipe, we are going to use both of them to implement a mapping data transformation. Let's imagine we are working on the part of the system responsible for managing university department lectures. We are given the following types:

class Course(val name: String, val lecturer: Lecturer, val isPaid: Boolean = false)
class Student(val name: String...