parsers

This should not only be part of code parsers, but of any parsers.

Then I implemented a little grammar for a shorthand to define parsers, and did the cst -> parser step to make it spit out working parsers.

A great next step would be combining it with work on formal verification of parsers or generators (see below).

Something cool about parsers is how many practical uses there are, and how easy they are to play with.

The hard part for me was visualising the pattern for more complicated types like parsers (functions from strings to results) and continuations.

My recent interest in parsers was those verified for correctness or security.

A solid understanding of parsers, lexers, and syntax trees would be an excellent place to start if you're interested in writing your own language.

Apache is a web server that add parsers as modules (php).

The Parboiled2 framework is often used for building parsers.

So, to start with, you'd have dozens of UI frameworks, network libraries, parsers, etc on your system.

Monads are a fantastic way of handling errors, composing parsers, handling concurrency, parallelism, callbacks, and many other non-IO related things.

It's often cited to be best for making language parsers using Parsec or Attoparsec, but I've found with Snap/Yesod/Scotty it is great for web development.

What sounds most interesting to me is that it seems to be kinda "dialect-oriented" -- meaning that to use it idiomatically, you should get used to writing tiny parsers (with provided toolbox) for small ad-hoc DSLs.

IO, State, Parsers, and STM are useful monads for which the collection metaphor doesn't seem to be particularly helpful.

Parsers of multimedia formats often have nasty vulnerabilities though.