I've been using Elm a lot lately, so I'm going to write down a series of posts of findings, thoughts and observations, both small & large, on concepts and corners of Elm that I feel are easy to overlook, counterintuitive or generally assumed to be known from previous Functional Programming experience.

Many people come from an OOP and Javascript background straight to Elm, so I'm going to also look at some things that are already familiar to people who have used ML or other FP languages.

Hopefully there'll be something for everyone.
I'll be updating this post with any new posts in this series, so it will work as a Table of Contents.

Table of Contents

• Currying, The Unknown
• let and in
• Destructuring
• Structuring your application
• The Strange Case of "<~"
• Pipes, Chaining and Nesting
• Next: coming soon

Version Migration

• Migrating from Elm 0.16 to 0.17 - from StartApp

Getting Elm up and running

If you haven't set Elm on your machine yet, here are a few guides which may prove useful:

• How to setup your local development environment for Elm from source
• What to do with your new Elm install
• Emacs setup for Elm (with autocompletion and lint)
• Video: elm-reactor: a Time Travelling Debugger

Comments? Give me a shout at @lambda_cat.
To get the latest post updates subscribe to the LambdaCat newsletter.
You can support my writing on LambdaCat's Patreon.