Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Learning Elixir
  • Toc
  • feedback
Learning Elixir

Learning Elixir

By : Kenny Ballou, Kenneth Ballou
5 (1)
close
Learning Elixir

Learning Elixir

5 (1)
By: Kenny Ballou, Kenneth Ballou

Overview of this book

Elixir, based on Erlang’s virtual machine and ecosystem, makes it easier to achieve scalability, concurrency, fault tolerance, and high availability goals that are pursued by developers using any programming language or programming paradigm. Elixir is a modern programming language that utilizes the benefits offered by Erlang VM without really incorporating the complex syntaxes of Erlang. Learning to program using Elixir will teach many things that are very beneficial to programming as a craft, even if at the end of the day, the programmer isn't using Elixir. This book will teach you concepts and principles important to any complex, scalable, and resilient application. Mostly, applications are historically difficult to reason about, but using the concepts in this book, they will become easy and enjoyable. It will teach you the functional programing ropes, to enable them to create better and more scalable applications, and you will explore how Elixir can help you achieve new programming heights. You will also glean a firm understanding of basics of OTP and the available generic, provided functionality for creating resilient complex systems. Furthermore, you will learn the basics of metaprogramming: modifying and extending Elixir to suite your needs.
Table of Contents (11 chapters)
close
10
Index

Branching with Elixir

A lot of languages have a staple in their language as the traditional branching structure, some form of "IF some condition is true THEN perform some statement ELSE do some different statement". Typically, then, if and else become keywords of the language; they are reserved and can only be used in the formation of branching statements.

Programming if condition then else is simply a way to express a fork in the execution path. We are saying, based on some condition, we should either execute one set of instructions or another. But as we saw before, pattern matching is quite expressive to this end. Based on structural or value matching, we can execute one version of a function, or another. What motivation, then, is there for expressions such as if true do x = 42 end? The expressiveness of pattern matching is occasionally too high-level when expressed in terms of functions. We need something that is closer together, but still expressively simple and easy to reason...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete