caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kakadu <kakadu.hafanana@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml release 4.02.0+beta1
Date: Wed, 21 May 2014 17:25:08 +0400	[thread overview]
Message-ID: <CAGmVoG0bA4dRU1kUF1Xj5NUuT45OhvrEdWXPgWxEb==d=z1E9A@mail.gmail.com> (raw)
In-Reply-To: <537CA058.5060306@mpi-sws.org>

Where should I look for labltk now?


Kakadu

On Wed, May 21, 2014 at 4:47 PM, Andreas Rossberg <rossberg@mpi-sws.org> wrote:
> On 21.05.2014 14:13, Damien Doligez wrote:
>>
>> OCaml 4.02.0+beta1:
>> -------------------
>
>
>> - Allow opening a first-class module [...]  in the body of
>>
>>    an applicative functor if no types are created
>
>
> Is that a good idea? It seems that one property you want from modules
> (second or first class) is that you can always extend them safely to a
> subtype (as a form of weakening). That property would be violated by such a
> typing rule, because extending a first-class module with a type might now
> unexpectedly break client code which unpacks it inside a functor, and relies
> on that functor being applicative.
>
> (Of course, 'open' and 'include' already violate this property, but they
> stick out enough and are known to be brittle.)
>
> /Andreas
>
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2014-05-21 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 12:13 Damien Doligez
2014-05-21 12:47 ` Andreas Rossberg
2014-05-21 13:25   ` Kakadu [this message]
2014-05-22 11:13     ` Damien Doligez
2014-05-22 14:30       ` Jacques Garrigue
2014-05-25 20:34 ` Christophe Raffalli
2014-05-25 21:39   ` Dmitry Grebeniuk
2014-06-18  9:55 ` Anil Madhavapeddy
2014-06-28  7:58 ` Christophe Raffalli
2014-06-30 13:10   ` Leo White

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='CAGmVoG0bA4dRU1kUF1Xj5NUuT45OhvrEdWXPgWxEb==d=z1E9A@mail.gmail.com' \
    --to=kakadu.hafanana@gmail.com \
    --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).