Book Image

Learn Type-Driven Development

By : Yawar Amin, Kamon Ayeva
Book Image

Learn Type-Driven Development

By: Yawar Amin, Kamon Ayeva

Overview of this book

Type-driven development is an approach that uses a static type system to achieve results including safety and efficiency. Types are used to express relationships and other assumptions directly in the code, and these assumptions are enforced by the compiler before the code is run. Learn Type-Driven Development covers how to use these type systems to check the logical consistency of your code. This book begins with the basic idea behind type-driven development. You’ll learn about values (or terms) and how they contrast with types. As you progress through the chapters, you’ll cover how to combine types and values inside modules and build structured types out of simpler ones. You’ll then understand how to express choices or alternatives directly in the type system using variants, polymorphic variants, and generalized algebraic data types. You’ll also get to grips with sum types, build sophisticated data types from generics, and explore functions that express change in the types of values. In the concluding chapters, you’ll cover advanced techniques for code reuse, such as parametric polymorphism and subtyping. By end of this book, you will have learned how to iterate through a type-driven process of solving coding problems using static types, together with dynamic behavior, to obtain more safety and speed.
Table of Contents (12 chapters)

Tuple types

Tuples are lightweight, structural types. To be precise, they are types made up of other types, joined together within parentheses in a particular order, separated by commas, and without field names. The tuple value syntax is very simple–open parenthesis, comma-separated list of values, close parenthesis. In fact, the value syntax closely mimics the type of the tuples themselves.

Tuple pronunciation varies depending on who you ask, but I usually pronounce it to rhyme with couple.

Why would we use tuples when we have record types with field names? Sometimes, we don't want to spin up a new type, with a definition, just to hold some values together. Tuples are a low-ceremony way to do that. But the danger of using them over larger portions of a codebase is that they're not self-describing like record types are. Here's an example:

/* src/Ch04/Ch04_Tuples...