It's a lot like programming haskell (which is not surprising given that carp is written in haskell, and utilises haskell's type system to achieve some things),

It's a lot like programming haskell (which is not surprising given that carp is written in haskell, and utilises haskell's type system to achieve some things), in that you'll find something is going fine for a while, then suddenly you hit a wall where you're not sure why the type system is rejecting what you want to do and suddenly you feel out of your depth. For example, trying to parse command line arguments ends up a bit weird because there's no 'return the command line arguments as a list/array' function, but you have to use Array.copy-map to run System.get-arg on each element of an array created by `(Array.range 0 (- @(System.get-args-len) 1))` and inferring the @s in there (a syntactic sugar for `(copy ...)` is a little confusing.