From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Alain Frisch <alain.frisch@lexifi.com>,
Romain Bardou <romain@cryptosense.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Newbie comment on constructor syntax
Date: Tue, 10 Nov 2015 11:17:06 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE3EE3A@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <5641CA8E.4060909@lexifi.com>
Dear Alain,
> Moreover, I'm not sure about the benefit: how often do you need to
> partially apply a constructor? And it's easy to define manually the helper
> function (let a x y = A (x, y)) if needed. I don't think adding dedicated syntax
> is justified here.
I see the main benefit of an explicit syntax for "constructor term" vs "currying constructor function" vs "tuple constructor function" in making it obvious that there is such a distinction.
I would agree with Romain, that for record fields a "functionify" operator would be of more practical use and also that it would also make sense to use the same "functionify" operator for different constructs which are not functions but have some obvious conversion into functions.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2015-11-10 11:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 9:33 Soegtrop, Michael
2015-11-06 10:04 ` Nicolas Ojeda Bar
2015-11-06 10:31 ` Francois Berenger
2015-11-06 12:20 ` Soegtrop, Michael
2015-11-06 12:34 ` Gabriel Scherer
2015-11-06 13:09 ` Soegtrop, Michael
2015-11-06 14:10 ` Ashish Agarwal
2015-11-06 15:19 ` Soegtrop, Michael
2015-11-06 15:21 ` Ashish Agarwal
2015-11-21 17:24 ` [Caml-list] Notation for currying Hendrik Boom
2015-11-21 17:41 ` Gabriel Scherer
2015-11-21 18:05 ` David Rajchenbach-Teller
2015-11-21 18:55 ` Gabriel Scherer
2015-11-06 12:29 ` [Caml-list] Newbie comment on constructor syntax Jonas Jensen
2015-11-06 12:46 ` Soegtrop, Michael
2015-11-06 12:54 ` Gabriel Scherer
2015-11-08 21:16 ` Florian Weimer
2015-11-08 22:50 ` Norman Hardy
2015-11-09 6:27 ` Florian Weimer
2015-11-09 13:27 ` Stefan Monnier
2015-11-09 8:09 ` Soegtrop, Michael
2015-11-09 10:00 ` Hendrik Boom
2015-11-09 10:16 ` Alain Frisch
2015-11-09 10:35 ` Andreas Rossberg
2015-11-09 12:28 ` Alain Frisch
2015-11-09 17:33 ` Alain Frisch
2015-11-09 18:08 ` Gabriel Scherer
2015-11-09 18:16 ` Andreas Rossberg
2015-11-09 21:11 ` Gabriel Scherer
2015-11-09 22:06 ` Alain Frisch
2015-11-09 22:27 ` Andreas Rossberg
2015-11-09 22:57 ` Jeremy Yallop
2015-11-10 0:11 ` Hendrik Boom
2015-11-10 8:27 ` Soegtrop, Michael
2015-11-10 10:25 ` Romain Bardou
2015-11-10 10:44 ` Alain Frisch
2015-11-10 10:55 ` Romain Bardou
2015-11-10 13:17 ` Alain Frisch
2015-11-10 13:41 ` Romain Bardou
2015-11-10 14:01 ` Alain Frisch
2015-11-13 15:36 ` Romain Bardou
2015-11-10 11:17 ` Soegtrop, Michael [this message]
2015-11-10 14:11 ` Hendrik Boom
2015-11-10 14:40 ` immanuel litzroth
2015-11-10 15:30 ` Soegtrop, Michael
2015-11-10 17:27 ` Gerd Stolpmann
2015-11-09 20:32 ` Alain Frisch
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=0F7D3B1B3C4B894D824F5B822E3E5A172CE3EE3A@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=alain.frisch@lexifi.com \
--cc=caml-list@inria.fr \
--cc=romain@cryptosense.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