caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Why isn't -rectypes command line option the default
Date: Wed, 21 Mar 2007 13:47:34 +0100	[thread overview]
Message-ID: <1174481255.11709.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20070321131334.e381b5fb.mle+ocaml@mega-nerd.com>

Am Mittwoch, den 21.03.2007, 13:13 +1100 schrieb Erik de Castro Lopo:
> Zheng Li wrote:
> 
> > So the main consideration is safety, though it's really fun to play with
> > recursive types sometimes.
> 
> Ok, I can see why they aren't on by default, but using -rectypes on 
> the whole file exposes to the whole file to these errors.
> 
> Wouldn't it be nicer to be able to specify the rectypes behaviour
> per type? Maybe something like this would work:
> 
> 	rec type 'a t = 'a * 'a t Lazy.t

You can do that:

type 'a t = T of 'a * 'a t Lazy.t

Recursive types are accepted without -rectypes when the recursion
crosses a variant type. Note that the runtime costs are usually
negligible.

Gerd
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
Phone: +49-6151-153855                  Fax: +49-6151-997714
------------------------------------------------------------


      parent reply	other threads:[~2007-03-21 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21  0:34 Erik de Castro Lopo
2007-03-21  1:48 ` Zheng Li
2007-03-21  2:13   ` [Caml-list] " Erik de Castro Lopo
2007-03-21  5:37     ` james woodyatt
2007-03-21  7:08       ` Erik de Castro Lopo
2007-03-21  9:01     ` Ville-Pertti Keinonen
2007-03-21 12:47     ` Gerd Stolpmann [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=1174481255.11709.23.camel@localhost.localdomain \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=mle+ocaml@mega-nerd.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).