caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Leo White <leo@lpw25.net>
To: Alain Frisch <alain.frisch@lexifi.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] exception Foo = Bar.Baz
Date: Wed, 27 Jul 2016 04:19:02 -0400	[thread overview]
Message-ID: <1469607542.3786388.677997945.214F613E@webmail.messagingengine.com> (raw)
In-Reply-To: <14e4dd61-7ff6-fdef-c103-a33c4f728bd9@lexifi.com>

> 
> So: do people see some use in being able to rename extension constructors?
> 

Renaming extension constructors can definitely be useful. Essentially, it is required
if you want to have an extension constructor as the parameter or result of some
function.

The testsuite contains such an example:

  https://github.com/ocaml/ocaml/blob/trunk/testsuite/tests/typing-extensions/msg.ml

In that example, the function is a functor which returns fresh constructors. The name of
this constructor is just `C` since the functor does not know what the constructor
represents, but it can then be renamed to something more suitable.

Regards,

Leo

  parent reply	other threads:[~2016-07-27  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 14:34 Matej Kosik
2016-07-25 20:02 ` Alain Frisch
2016-07-25 20:05   ` Gabriel Scherer
2016-07-26  9:36     ` Leo White
2016-07-26 12:37       ` Gabriel Scherer
2016-07-26 16:27         ` Alain Frisch
2016-07-26 16:32           ` Gabriel Scherer
2016-07-27  8:07             ` Alain Frisch
2016-07-27  8:27               ` Gabriel Scherer
2016-07-27  8:38                 ` Alain Frisch
2016-07-27  8:19           ` Leo White [this message]
2016-07-26  9:02   ` Matej Kosik
2016-07-26 12:13     ` 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=1469607542.3786388.677997945.214F613E@webmail.messagingengine.com \
    --to=leo@lpw25.net \
    --cc=alain.frisch@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@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).