caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mike Potanin <potanin@mccme.ru>
To: caml-list@inria.fr
Subject: Re: [Caml-list] let rec
Date: Sat, 18 Jan 2003 18:31:13 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.44.0301181822440.723-100000@mccme.ru> (raw)
In-Reply-To: <9D69A846-2ADD-11D7-AFEF-0003930FCE12@inria.fr>

On Sat, 18 Jan 2003, Damien Doligez wrote:

> On Thursday, January 16, 2003, at 03:38 PM, Mike Potanin wrote:
>
> > The similar problem arises in a case
> > let ring l = let rec r = l@r in r
> > OCaml type system can not understand that the design is safe.
>
> But it is not unconditionally safe.  Its safety depends on how
> you defined the @ function.  O'Caml doesn't want to look at
> the definition of @ because separate compilation is a very
> important feature.

If extend type model compiler can handle this case. The type of @ function
may content information "this function is realy lazy for second argument".
This don't handle all case recurcive data, but impotant case.
Mercury language don't handle all "modes" too :-).

>
> -- Damien

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-01-18 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 19:15 Vitaly Lugovsky
2003-01-15 19:27 ` james woodyatt
2003-01-15 19:54   ` Vitaly Lugovsky
2003-01-15 19:53 ` Max Kirillov
2003-01-16 14:38 ` Mike Potanin
2003-01-18 12:08   ` Damien Doligez
2003-01-18 15:31     ` Mike Potanin [this message]
2003-01-18 19:22     ` Vitaly Lugovsky

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=Pine.LNX.4.44.0301181822440.723-100000@mccme.ru \
    --to=potanin@mccme.ru \
    --cc=caml-list@inria.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).