From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] How much optimized is the 'a option type ?
Date: Wed, 29 Jan 2014 11:11:49 -0500 [thread overview]
Message-ID: <CAN6ygO=YLesg_jX5UF=dQAS3n2th=8ELhFMYffmnSwPAB7DoNA@mail.gmail.com> (raw)
In-Reply-To: <02c001cf1ccc$b635a9b0$22a0fd10$@ffconsultancy.com>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
On Wed, Jan 29, 2014 at 3:32 AM, Jon Harrop <jon@ffconsultancy.com> wrote:
> Yotam wrote:
> > Of course, once you unbox, all parametric polymorphism is lost
>
> Is it?
>
>
It is in haskell. In general, I don't think you can do any parametric
polymorphism without metadata.
> You would have to box the tuple before passing it to a polymorphic function
> with the type 'a -> 'a. However, if the function has the type 'a * 'b -> 'b
> * 'a then you could always unbox, right?
>
>
I don't think so. Without metadata, how do you know where one tuple member
ends and another begins?
Yotam
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
next prev parent reply other threads:[~2014-01-29 16:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 7:35 Damien Guichard
2014-01-17 7:55 ` David House
2014-01-17 8:16 ` Julien Blond
2014-01-17 8:40 ` David House
2014-01-17 9:10 ` Gabriel Scherer
2014-01-17 9:22 ` Simon Cruanes
2014-01-17 17:57 ` Gerd Stolpmann
2014-01-18 1:35 ` Jon Harrop
2014-01-19 6:19 ` oleg
2014-01-21 1:51 ` Francois Berenger
2014-01-18 1:01 ` Jon Harrop
2014-01-24 10:06 ` Alain Frisch
2014-01-24 10:16 ` Alain Frisch
2014-01-24 13:32 ` Yaron Minsky
[not found] ` <CAK=fH+jfi=GsMYBZzmuo=V5UAWimyxiiamY2+DkLg6F0i8XHGw@mail.gmail.com>
2014-01-17 9:11 ` David House
2014-01-17 11:23 ` Jonathan Kimmitt
2014-01-17 13:46 ` Nicolas Braud-Santoni
2014-01-17 13:56 ` Frédéric Bour
2014-01-17 14:02 ` Yaron Minsky
2014-01-17 14:09 ` Simon Cruanes
2014-01-17 22:52 ` Yaron Minsky
2014-01-18 1:37 ` Jon Harrop
2014-01-17 14:24 ` Gabriel Scherer
2014-01-17 22:29 ` Yaron Minsky
2014-01-18 1:27 ` Jon Harrop
2014-01-18 1:18 ` Jon Harrop
2014-01-20 10:16 ` Goswin von Brederlow
2014-01-20 11:23 ` Jonathan Kimmitt
2014-01-21 2:05 ` Francois Berenger
2014-01-22 21:22 ` Jon Harrop
2014-01-22 21:26 ` Jon Harrop
2014-01-23 9:29 ` Goswin von Brederlow
2014-01-23 23:20 ` Jon Harrop
2014-01-23 23:28 ` Yotam Barnoy
2014-01-24 8:22 ` Jon Harrop
2014-01-24 8:34 ` Andreas Rossberg
2014-01-24 16:56 ` Jon Harrop
2014-01-27 15:29 ` Goswin von Brederlow
2014-01-27 16:18 ` Yotam Barnoy
2014-01-29 7:56 ` Goswin von Brederlow
2014-01-29 8:32 ` Jon Harrop
2014-01-29 16:11 ` Yotam Barnoy [this message]
2014-01-30 18:43 ` Yotam Barnoy
2014-02-01 15:58 ` Goswin von Brederlow
2014-01-30 21:31 ` Jon Harrop
2014-01-30 21:43 ` Yotam Barnoy
2014-01-31 8:26 ` Jon Harrop
2014-02-01 15:40 ` Goswin von Brederlow
2014-01-27 10:03 ` Goswin von Brederlow
2014-01-17 14:36 ` Markus Mottl
2014-01-17 15:49 ` Yotam Barnoy
2014-01-17 16:22 ` Markus Mottl
2014-01-20 10:09 ` Goswin von Brederlow
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='CAN6ygO=YLesg_jX5UF=dQAS3n2th=8ELhFMYffmnSwPAB7DoNA@mail.gmail.com' \
--to=yotambarnoy@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
--cc=jon@ffconsultancy.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).