Attila Gulyas

On page 30 (_Accounts_ > _Register a user_ > _Constructing commands from external data_) adding the `ExConstructor` package is missing a step (I think): adding it to `application` in `mix.exs`....

@OvermindDL1 expanded on "tuple calls" (see #25), and he also mentioned that it is going away. Returning anonymous functions with different arity heads is also an error. ```elixir iex(6)> fn...

A simple (but ugly) solution: ```elixir defmodule A do defmacro defpartialx({fun_name, ctx, args}, do: body) do scanned_args = [[]] ++ args_scan(args) quote do unquote do: make_curried_clauses(scanned_args, {fun_name, ctx, body}) end...

> Nix + nixpkgs One could argue that Nix "core" and Nixpkgs are separate as well: Nix "core" works with [alternative package sets](https://nixos.wiki/wiki/Alternative_Package_Sets), and Nixpkgs also works with alternate implementations...

+1 for linking source I do agree with @roberth that 1. linking to source in lieu of maintaining proper docs should be a no go \- except if it used...

Thank you for correcting my assumptions regarding haddock and for linking nixdoc because I missed it so far!

Commented about this in #2. See [comment](https://github.com/expede/algae/issues/2#issuecomment-469832588).

A Haskell or PureScript record would be a simple map in Elixir, right? So `type Username = { first :: String, last :: String}` would be `%Username{first: nil, last: nil}`...

Thanks! Yeah, I haven't really gotten to learn about row-types yet, but as you can read above, I just realized that `defdata` is really for product types and not records...

After a couple days, here's may take on #2 and #3, the way Haskell and PureScript smart constructors are working (based on my limited knowledge) where every type is responsible...