caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andreas Rossberg <rossberg@mpi-sws.org>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Arnaud Spiwack <Arnaud.Spiwack@lix.polytechnique.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] First-class module and higher-order types
Date: Sat, 20 Aug 2011 09:01:50 +0200	[thread overview]
Message-ID: <3F59E9D3-E0FF-4FC3-A737-39861831331B@mpi-sws.org> (raw)
In-Reply-To: <15C8C097-A8E2-4D96-AEEC-982DBEB65DD8@math.nagoya-u.ac.jp>

On Aug 20, 2011, at 05.26 h, Jacques Garrigue wrote:
> On 2011/08/20, at 0:38, Arnaud Spiwack wrote:
>> 	• On the theoretical side, how hard is it to design a variant of  
>> Hindley-Milner's typing algorithm with type-family quantification?  
>> (I understand that Ocaml's typing machinery is pretty hard to  
>> change, and that it will most likely not be happening any time soon  
>> in practice)
>
> Well, Haskell has higher-order type constructors, but its type  
> system is much less structural.
> In particular, I have no idea how this would interact with recursive  
> types.

Interesting. I'm curious. The essential restriction in Haskell is that  
universally quantified type variables of non-trivial kind can only be  
instantiated with nominal type constructors (in order to avoid the  
need for higher-order unification).  Shouldn't the same work for OCaml?

Or are you referring to type normalisation for (explicit) applications  
of higher-order type constructors? Given that OCaml only allows equi- 
recursion at base kind, how could it interact in interesting ways?

Thanks,
/Andreas



      reply	other threads:[~2011-08-20  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 15:38 Arnaud Spiwack
2011-08-20  3:26 ` Jacques Garrigue
2011-08-20  7:01   ` Andreas Rossberg [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=3F59E9D3-E0FF-4FC3-A737-39861831331B@mpi-sws.org \
    --to=rossberg@mpi-sws.org \
    --cc=Arnaud.Spiwack@lix.polytechnique.fr \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /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).