From: Keiko Nakata <keiko@kurims.kyoto-u.ac.jp>
To: jun.furuse@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Recursive module and class
Date: Sat, 12 Jul 2008 16:34:03 +0900 (JST) [thread overview]
Message-ID: <20080712.163403.68558844.keiko@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <87abgqbplw.wl%jun.furuse@gmail.com>
Hello.
To the best of my knowledge, there is subtle interaction
between typing of recursive modules and unfolding of recursive structural types,
i.e, classes and polymorphic variants.
I remember Jacques has hit a similar problem:
http://caml.inria.fr/pub/ml-archives/caml-list/2008/02/de4c1ddaa8bf3c0ef9350d8fb4f1e8f7.en.html
My understanding is that with recursive modules you may define two types
that are equivalent but do not join together by simple unfolding
of abbreviations; this seems to confuse the type checker.
I believe this is a known bug of the current implementation
of the type checker.
With best regards,
Keiko
prev parent reply other threads:[~2008-07-12 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 23:32 Jun Furuse
2008-07-12 7:34 ` Keiko Nakata [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=20080712.163403.68558844.keiko@kurims.kyoto-u.ac.jp \
--to=keiko@kurims.kyoto-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=jun.furuse@gmail.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).