caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: "Milan Stanojević" <milanst@gmail.com>
Cc: OCaML List Mailing <caml-list@inria.fr>
Subject: Re: [Caml-list] variance/injectivity/uniqueness annotations for types
Date: Thu, 14 Apr 2016 18:56:47 +0900	[thread overview]
Message-ID: <94AF08A8-C9A5-4D0A-B8A4-4C27DA4F8C9B@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <CAKR7PS-ux0YihQRa+kpv_UZOXDiQm+GzYHOEXgwyzhFGt2FQWA@mail.gmail.com>

On 2016/03/11 15:53, Milan Stanojević wrote:
> 
> I ran into some variance/injectivty issues in my code, plus I saw some
> recent question here, and I was wondering if there was any progress on
> adding syntax so types can be annotated with proper information (as
> discussed in http://caml.inria.fr/mantis/view.php?id=5985).
> 
> I guess we don't really need new syntax, we can just use attributes
> (e.g. [@@unique] or [@@injective])
> 
> I searched mantis a bit but I don't see anything new (maybe I didn't
> search hard enough).


The situation seems to be stuck currently, waiting for concrete examples
where this is really needed, and also for a good syntax.
Indeed, in other discussions, there seemed to be an agreement that
attributes were not very good for changing the type system itself, as they
are somehow outside of the language. Moreover, injectivity would be rather
heavy, as this is a per-parameter property. Concerning uniqueness,
Alain Frisch made some interesting suggestion of using a global name or
path to make types distinguishable.

Jacques Garrigue

      reply	other threads:[~2016-04-14  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  6:53 Milan Stanojević
2016-04-14  9:56 ` Jacques Garrigue [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=94AF08A8-C9A5-4D0A-B8A4-4C27DA4F8C9B@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@inria.fr \
    --cc=milanst@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).