Book Overview & Buying
Table Of Contents

Learn Type-Driven Development

By : Soumya Mukherjee, Amin, Kamon Ayeva

5 (1)

Buy this Book

Learn Type-Driven Development

5 (1)

By: Soumya Mukherjee, Amin, Kamon Ayeva

Buy this Book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Starting Type-Driven Development

Analyzing code for hidden errors

Adding types

ReasonML

Summary

Programming with Types and Values

Workflow

Types and values

Static and dynamic environments

Errors

Summary

Packaging Types and Values Together

File modules

Syntactic modules

Module signatures

Module errors

Type abstraction

Summary

Grouping Values Together in Types

Record types

Tuple types

Object types

JavaScript object types

Summary

Putting Alternative Values in Types

Variant types

The power of switch

Polymorphic variant types

Generalized algebraic data types

Designing for correctness with types

Summary

Making Types That Can Slot into Any Other Type

Type inference and generic types

The list – modeling more than one

The option – modeling either none or one

Mutable parameterized types – ref and array

Forcing a difference with phantom types

Summary

Making Types That Represent Operations

Function types and other useful properties

Multiple arguments and currying

Summary

Reusing Code with Many Different Types

Polymorphism in Reason

Generic code with functors

Summary

Extending Types with New Behavior

Subtyping using polymorphic variants

Code reuse with OOP-style inheritance

Summary

Bringing It All Together

Starting with a variant type (version 1)

Using more pattern matching (version 2)

Switching to polymorphic variant types (version 3)

Using records (version 4)

Using modules for code structure (version 5)

An alternative code structure (version 6)

An improvement – using lists as output (version 7)

Another improvement – using mutable records (version 8)

Unit testing our code (final version)

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

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: