From: Arlen Cox <arlencox@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Applicative Functor Madness
Date: Thu, 20 Sep 2018 10:29:46 -0400 [thread overview]
Message-ID: <CAHEcMuF5waGp8Fs95XiGeJ=sS5p=CxUt=1V_50HUWQZKt6HuXQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2050 bytes --]
next reply other threads:[~2018-09-20 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 14:29 Arlen Cox [this message]
2018-09-20 16:02 ` Arlen Cox
2018-09-21 0:10 ` Jacques Garrigue
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='CAHEcMuF5waGp8Fs95XiGeJ=sS5p=CxUt=1V_50HUWQZKt6HuXQ@mail.gmail.com' \
--to=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