From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: ygrek <ygrekheretix@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] module alias inside class
Date: Wed, 3 Jul 2013 14:09:49 +0900 [thread overview]
Message-ID: <16D5DC66-9420-4B6F-B7CF-DF16161D2A6A@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <20130702230929.39fc70d3@kiwi.local.tld>
On 2013/07/03, at 0:09, ygrek <ygrekheretix@gmail.com> wrote:
> Dear list,
>
> Just a short question tonight, why is the following code rejected?
>
> class z = let module A = String in object end;;
>
> Is there some deep reason or it was simply overlooked?
This would be very nice to able to do that.
Unfortunately, the typing of classes is a rather complex process,
which seems difficult to integrate with local module definitions,
except maybe in a very restrictive way.
There are also deep questions, such as what to do in presence
of inheritance.
On the other hand, "let open" would be much easier to add.
Jacques Garrigue
next prev parent reply other threads:[~2013-07-03 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 15:09 ygrek
2013-07-03 5:09 ` Jacques Garrigue [this message]
2013-07-03 10:56 ` AW: " Gerd Stolpmann
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=16D5DC66-9420-4B6F-B7CF-DF16161D2A6A@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=ygrekheretix@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).