caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "John D. Barnett" <barnett@psrg.lcs.mit.edu>
To: caml-list@inria.fr
Subject: [Caml-list] unique record types
Date: Thu, 06 Jun 2002 22:03:35 -0400	[thread overview]
Message-ID: <3D001477.4080605@psrg.lcs.mit.edu> (raw)

The ocaml documentation mentions that field names in a record must be 
unique (within a module), although the ocaml book mentions an 
experimental language feature to get around this, that seems no longer 
available.

My question is, why is this so?  Can anyone recommend a paper explaining 
difficulties/solutions to implementing record types in the ML-style type 
system?

Thanks,

-John

-------------------
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:[~2002-06-07  1:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3D001477.4080605@psrg.lcs.mit.edu \
    --to=barnett@psrg.lcs.mit.edu \
    --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).