caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Boris Yakobowski <boris@yakobowski.org>
To: "Stéphane Gimenez" <stephane.gimenez@pps.jussieu.fr>,
	"The Caml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] type generalization of recursive calls
Date: Wed, 17 Feb 2010 20:41:07 +0100	[thread overview]
Message-ID: <76c7f53f1002171141y68374f94u11d0ac807ccfee89@mail.gmail.com> (raw)
In-Reply-To: <20100217163424.GA38458@tenebreuse>

Hi Gim,

On Wed, Feb 17, 2010 at 5:34 PM, Stéphane Gimenez
<stephane.gimenez@pps.jussieu.fr> wrote:
> Questions:
>  - Is it theoreticaly safe to generalize recursive calls ?

Yes. And this is done in explicitly-typed languages, such as in Coq.

>  - Is there a syntactical trick to use generalized recursive calls ?

Not in the current Ocaml, as type annotations cannot be used to
introduce type polymorphism. However, see below.

>  - Could such a generalization be added to the type checker ?
>      - Performance issues ?
>      - More obfusctated type checking errors ?

Unfotunately, it is worse than that : type inference is undecidable in
the presence of polymorphic recursion. See e.g.
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.42.3091

> In a related disscution I found, one asked about generalization
> between mutualy recursive definitions (same problem). No answers, but
> maybe I just lack pointers.

If I'm not mistaken, you can encode all cases of polymorphic recursion
using mutual monomorphic recursion. For your example, this would give

let rec map f = function
  | E -> E
  | D (t1, t2) -> D (map f t1, map f t2)
  | O a -> O (f a)
  | I tt -> I (map2 (map f) tt)
and map2 x = map x

Here, map is always called with type ('a -> 'b) -> 'a t -> 'b t inside
its own body (and is instantiated only inside map2). Thus this second
problem is even harder than polymorphic recursion.

Finally, starting from Ocaml 3.13, you can simply write

let rec map : 'a 'b. ('a -> 'b) -> 'a t -> 'b t = fun f -> function
  | E -> E
  | D (t1, t2) -> D (map f t1, map f t2)
  | O a -> O (f a)
  | I tt -> I (map (map f) tt)

Hope this helps,

-- 
Boris


  reply	other threads:[~2010-02-17 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 16:34 Stéphane Gimenez
2010-02-17 19:41 ` Boris Yakobowski [this message]
2010-02-17 20:25   ` [Caml-list] " Dario Teixeira
2010-02-17 20:33     ` Boris Yakobowski
2010-02-18 14:24 ` Stéphane Gimenez
2010-02-17 17:59 [Caml-list] " Damien Guichard
2010-02-17 18:13 Damien Guichard

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=76c7f53f1002171141y68374f94u11d0ac807ccfee89@mail.gmail.com \
    --to=boris@yakobowski.org \
    --cc=caml-list@inria.fr \
    --cc=stephane.gimenez@pps.jussieu.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;
as well as URLs for NNTP newsgroup(s).