From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: Arlen Cox <arlencox@gmail.com>
Cc: Mailing List OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Applicative Functor Madness
Date: Fri, 21 Sep 2018 09:10:25 +0900 [thread overview]
Message-ID: <F5788BC4-5C8E-4D11-86AF-5D3EE67E44FA@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <CAHEcMuF5waGp8Fs95XiGeJ=sS5p=CxUt=1V_50HUWQZKt6HuXQ@mail.gmail.com>
A first remark: this use of module type of is probably not a good idea in the long term, as module type of is brittle, and its semantics could change.
Then why it doesn’t work: for soundness reasons, module aliases to functor arguments are not allowed, so actually in the body of the functor T and T_in are not equal, they are just modules with the same signature, so of course Set.Make(T).t and Set.Make(T_in).t are not equal.
A way around this limitation is to remove T from the return type:
module Make(T_in : Set.OrderedType) :
S with module T := T_in and module ST = Set.Make(T_in)
= struct module ST = Set.Make(T_in) end
Do you see a problem with this version?
Jacques Garrigue
On 2018/09/20 23:29, Arlen Cox wrote:
>
> Hi everyone,
>
> I'm having some trouble getting some code that relies heavily on applicative functors to type check. Does anyone know what I'm doing wrong with this?
>
> module type S = sig
> module T : Set.OrderedType
> module ST : module type of Set.Make(T)
> end
>
> module Make(T_in : Set.OrderedType) : S (* <- ERROR *)
> with module T = T_in
> and module ST = Set.Make(T_in)
> = struct
> module T = T_in
> module ST = Set.Make(T_in)
> end
>
> I get the following error message referencing the above point in the program.
>
> Error: In this `with' constraint, the new definition of ST
> does not match its original definition in the constrained signature:
> ...
> Type declarations do not match:
> type t = Set.Make(T_in).t
> is not included in
> type t = Set.Make(T).t
> File "set.mli", line 68, characters 4-10: Expected declaration
> File "set.mli", line 68, characters 4-10: Actual declaration
>
> It seems to me that since T = T_in, but applicative functors should make the type of Set.Make(T) = Set.Make(T_in). Does this not work this way?
>
> Note that if I change the definition of S slightly, the same definition of Make now type checks:
>
> module type S = sig
> module T : Set.OrderedType
> module ST : Set.S with type elt = T.t
> end
>
> This solution is undesirable because I have a number of modules whose types would require an excessive number of "with module ... = ..." constraints to constrain in this way. Is there a better way of getting this to type check?
>
> Thank you,
> Arlen
>
>
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2018-09-21 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 14:29 Arlen Cox
2018-09-20 16:02 ` Arlen Cox
2018-09-21 0:10 ` Jacques Garrigue [this message]
2018-09-21 1:25 ` Arlen Cox
2018-09-21 5:54 ` Jacques Garrigue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F5788BC4-5C8E-4D11-86AF-5D3EE67E44FA@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=arlencox@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).