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.
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
- Structuring your application
- The Strange Case of "<~"
- Pipes, Chaining and Nesting
- Next: coming soon
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