From: Jiten Pathy <jpathy@fssrv.net>
To: Jeremy Yallop <yallop@gmail.com>
Cc: Stephen Dolan <stephen.dolan@cl.cam.ac.uk>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] phantom type
Date: Mon, 27 Apr 2015 21:35:29 -0700 [thread overview]
Message-ID: <CAL2Z3DA46S3Q9pbWF-L9WVMNijdw0UbSczbfmwjN5ViXVKf+CA@mail.gmail.com> (raw)
In-Reply-To: <CAAxsn=FomDwmm=2RO3gGsN9ZirB4XE2POzZ9LxcefqFzDG1kfw@mail.gmail.com>
No, it was just a speculation as a new record is created for every
sub-term evaluation.
On Mon, Apr 27, 2015 at 5:30 AM, Jeremy Yallop <yallop@gmail.com> wrote:
> On 27 April 2015 at 13:17, Jiten Pathy <jpathy@fssrv.net> wrote:
>> It seems this encoding using first-class modules has overheads in the
>> interpreter(due to the functor), whereas the gadt implementation would
>> have no overheads.
>
> Have you measured it?
prev parent reply other threads:[~2015-04-28 4:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 10:23 Jiten Pathy
2015-04-27 10:36 ` Jeremy Yallop
2015-04-27 11:32 ` Jiten Pathy
2015-04-27 11:51 ` Stephen Dolan
2015-04-27 12:17 ` Jiten Pathy
2015-04-27 12:30 ` Jeremy Yallop
2015-04-28 4:35 ` Jiten Pathy [this message]
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=CAL2Z3DA46S3Q9pbWF-L9WVMNijdw0UbSczbfmwjN5ViXVKf+CA@mail.gmail.com \
--to=jpathy@fssrv.net \
--cc=caml-list@inria.fr \
--cc=stephen.dolan@cl.cam.ac.uk \
--cc=yallop@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).