Good point -- wasn't looking at the map.mli file. Thanks.

Yotam


On Wed, Aug 27, 2014 at 10:59 AM, Leo White <lpw25@cam.ac.uk> wrote:
>
> Can anyone tell me why the compiler complained about Empty being an unbound constructor when it's declared in Map.Make,
> which I include?
>

I don't think `Empty` is declared in the interface of Map.Make, it may
be declared in the implementation but it is not available in the
interface. Making it available in the interface would break abstraction:
it would force `Map.Make` to keep using that particular implementation.

Regards,

Leo