From: Oleg <oleg@okmij.org>
To: zhenya1007@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] A question about "8.9 First-class modules -> Advanced
Date: Wed, 27 Dec 2017 16:56:37 +0900 [thread overview]
Message-ID: <20171227075637.GA999@Magus.localnet> (raw)
In-Reply-To: <CAGYXaSb5mXa33R7RccEeqh8aYEgow8OtG9VctVOono6x0hgW1Q@mail.gmail.com>
> I appreciate that it may be, "possible to parametrize some code over the
> implementation of a module without using a functor", but I am having
> trouble imagining why one would want to do such a thing.
Here is an example why one may want to do such thing
http://okmij.org/ftp/tagless-final/nondet-effect.html#no-functor
In fact, tagless-final approach lends itself very well to first-class
modules.
next prev parent reply other threads:[~2017-12-27 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 9:13 [Caml-list] A question about "8.9 First-class modules -> Advanced examples" section of the reference manual Evgeny Roubinchtein
2017-12-27 7:56 ` Oleg [this message]
2018-01-03 10:22 ` Nicolás Ojeda Bär
2018-01-03 10:47 ` Xavier Leroy
2018-01-03 14:43 ` Nicolás Ojeda Bär
2018-01-04 16:50 ` Hao Wu
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=20171227075637.GA999@Magus.localnet \
--to=oleg@okmij.org \
--cc=caml-list@inria.fr \
--cc=zhenya1007@gmail.com \
/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).