When set up, protect master branch.

Tending towards Result because it fits better into existing infrastructure.

It's not clear whether functors like Monad should return a module that includes the base module's signature or not. Sometimes it feels more convenient if they do, e.g. Option monad below, one the other hand it gets tedious to add include Monad(Foo) with type 'a t := 'a t all the time.

(* without base module *)
module Option = struct
  type 'a t = 'a option
  include Monad (
    struct
      type 'a t = 'a option
      let return x = Some x
      let bind f x = match x with Some v -> f v | None -> None
    end)
end

(* with base module *)
module Option = Monad (
    struct
      type 'a t = 'a option
      let return x = Some x
      let bind f x = match x with Some v -> f v | None -> None
    end)

• move out of functor example
• add more motivation
• cover all functions
  • cata/ana
  • hylo
  • para/apo
  • histo/futu
  • zygo

• Lemonade
• OLMI
• monadlib
• lens?

The current flat structure might scare people who look at the signature.

Maybe https://github.com/ocaml-ppx/ppx_deriving.

• fmt
• logs
• lwt
• mparser
• lens?

Aside: how do optional dependencies work?

i.e. can they be used in real code? See #2.

Modules for which any of the following holds should go there:

• no examples
• untested
• usage unclear
• API might change