caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: David.Teller@ens-lyon.org
Cc: Yitzhak Mandelbaum <yitzhakm@cs.princeton.edu>,
	OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] optional functions in modules
Date: Fri, 18 May 2012 18:00:13 +0200	[thread overview]
Message-ID: <CAPFanBFm-0aSWtVS8BX2AuFjEFuxEweWQVp9bp7f0pXTE+_P-A@mail.gmail.com> (raw)
In-Reply-To: <4FB669B4.6000200@ens-lyon.org>

You can regain that polymorphism at a moderate efficiency cost by eta-expanding:

   let mmap2 f = match mmap with | None -> failwith "Nope" | Some x -> x f;;
   val mmap2 : ('a -> 'b) -> 'a list -> 'b list = <fun>

On Fri, May 18, 2012 at 5:24 PM, David Rajchenbach-Teller
<David.Teller@ens-lyon.org> wrote:
> On 5/17/12 7:43 PM, Yitzhak Mandelbaum wrote:
>> Thanks to everyone who responded.  FWIW, I found the argument in favor of options most compelling as a general approach.
>>
>> Yitzhak
>>
>
> Note that there is a drawback to that approach: loss of polymorphism.
>
> # let mmap = Some List.map;;
> val mmap : (('a -> 'b) -> 'a list -> 'b list) option = Some <fun>
>
> # let mmap2 = match mmap with | None -> failwith "Nope" | Some x -> x;;
> val mmap2 : ('_a -> '_b) -> '_a list -> '_b list = <fun>
>
> I suspect that first-class modules can help here, but I have not really
> had time to toy with them yet.
>
> Cheers,
>  David
>

  reply	other threads:[~2012-05-18 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 12:22 Yitzhak Mandelbaum
2012-05-10 14:13 ` "Markus W. Weißmann"
2012-05-10 14:53 ` Fabrice Le Fessant
2012-05-10 14:59   ` David Rajchenbach-Teller
2012-05-10 18:44 ` Goswin von Brederlow
2012-05-11  0:55   ` Yaron Minsky
2012-05-17 17:43     ` Yitzhak Mandelbaum
2012-05-18 15:24       ` David Rajchenbach-Teller
2012-05-18 16:00         ` Gabriel Scherer [this message]
2012-05-18 20:05           ` Nicolas Braud-Santoni

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=CAPFanBFm-0aSWtVS8BX2AuFjEFuxEweWQVp9bp7f0pXTE+_P-A@mail.gmail.com \
    --to=gabriel.scherer@gmail.com \
    --cc=David.Teller@ens-lyon.org \
    --cc=caml-list@inria.fr \
    --cc=yitzhakm@cs.princeton.edu \
    /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).