Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Learning Functional Programming in Go
  • Table Of Contents Toc
  • Feedback & Rating feedback
Learning Functional Programming in Go

Learning Functional Programming in Go

By : Sheehan
4.1 (8)
close
close
Learning Functional Programming in Go

Learning Functional Programming in Go

4.1 (8)
By: Sheehan

Overview of this book

Lex Sheehan begins slowly, using easy-to-understand illustrations and working Go code to teach core functional programming (FP) principles such as referential transparency, laziness, recursion, currying, and chaining continuations. This book is a tutorial for programmers looking to learn FP and apply it to write better code. Lex guides readers from basic techniques to advanced topics in a logical, concise, and clear progression. The book is divided into four modules. The first module explains the functional style of programming: pure functional programming, manipulating collections, and using higher-order functions. In the second module, you will learn design patterns that you can use to build FP-style applications. In the next module, you will learn FP techniques that you can use to improve your API signatures, increase performance, and build better cloud-native applications. The last module covers Category Theory, Functors, Monoids, Monads, Type classes and Generics. By the end of the book, you will be adept at building applications the FP way.
Table of Contents (13 chapters)
close
close

A conversation - Java developer, idiomatic Go developer, FP developer

Developer

Says...

Java

I do not like the way Go makes me handle errors after every function call.

I want exception handling like this:

try {
Decrypt()
Authenticate()
Charge()
}
catch (Exception e) {
// handle exception
}

However, after adding all those error checks, my code looks like this:

err := Decrypt()
if err != nil {
return err
}
err = Authenticate()
if err != nil {
return err
}
Charge()

Go error handling looks like a bunch of scaffolding obscuring my code's intentions.

Go

As you know, Go does not support exception handling. Instead, you return errors to inform the calling function/method that something went wrong. You are supposed to handle an error as soon as possible. This is what we call the idiomatic way to handle errors. When you throw exceptions, how far up the call stack...

Subscribe to access the full title

Advance your knowledge in tech

A Packt subscription gives you instant online access to our library of over 8,000 practical eBooks and videos, constantly updated with the latest in tech
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon