From: =?gb18030?B?Qm9i?= <bob.hongbo.zhang@foxmail.com>
To: =?gb18030?B?eHJhbXRzb3Y=?= <xramtsov@gmail.com>,
=?gb18030?B?Y2FtbC1saXN0?= <caml-list@inria.fr>
Subject: Re: [Caml-list] ReasonML concrete syntax
Date: Mon, 11 Dec 2017 15:22:14 +0800 [thread overview]
Message-ID: <tencent_328F87040D5AB8198995C2DD09291F3D2C0A@qq.com> (raw)
In-Reply-To: <20171211095444.75abacda@zinid.ru>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1188 bytes --]
Let¡¯s be civil. Note that I did not write a single line of reason, but I understand it¡¯s intention to use a more familiar function application syntax and it seems to be appreciated by quite a few people.
There are issues though, the parens are overloaded in too many context, if it uses ¡®[¡® for tuple like what typescript did, then such ambiguity would be removed
·¢×ÔÎÒµÄiPhone
------------------ Original ------------------
From: Evgeny Khramtsov <xramtsov@gmail.com>
Date: ÖÜÒ»,12ÔÂ 11,2017 3:12 ÏÂÎç
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ReasonML concrete syntax
Mon, 11 Dec 2017 07:50:02 +0100
Sven SAULEAU <sven.sauleau@xtuc.fr> wrote:
> The reason behind that move (from Reasonml version 2 to 3), is that
> it feels more natural to JavaScript developers.
If you develop software for idiots, only idiots will use it (c)
Come on, if you cannot learn a new syntax, you're an idiot. No
exceptions.
--
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
[-- Attachment #2: Type: text/html, Size: 1704 bytes --]
next prev parent reply other threads:[~2017-12-11 7:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 18:12 Robert Muller
2017-12-11 0:09 ` Yawar Amin
2017-12-11 5:50 ` Viet Le
2017-12-11 6:45 ` Ian Zimmerman
2017-12-11 6:53 ` Sven SAULEAU
2017-12-11 6:50 ` Sven SAULEAU
2017-12-11 6:54 ` Evgeny Khramtsov
2017-12-11 7:22 ` =?gb18030?B?Qm9i?= [this message]
2017-12-11 7:16 ` Evgeny Khramtsov
2017-12-17 15:02 ` Paolo Donadeo
2017-12-17 16:01 ` Guillaume Huysmans
2017-12-17 16:55 ` Paolo Donadeo
2017-12-17 20:13 ` Ian Zimmerman
2017-12-17 20:49 ` Robert Muller
2017-12-18 1:34 ` Yawar Amin
2017-12-18 16:36 ` Evgeny Khramtsov
2017-12-18 17:00 ` Jesper Louis Andersen
2017-12-18 17:27 ` Gary Trakhman
2017-12-18 17:53 ` Evgeny Khramtsov
2017-12-18 2:14 ` Yawar Amin
2017-12-11 15:51 ` Yawar Amin
2017-12-11 16:07 ` Sven SAULEAU
2017-12-11 17:11 ` David Brown
2017-12-12 3:49 ` Louis Roché
2017-12-12 4:18 ` Yawar Amin
2017-12-12 5:52 ` Oliver Bandel
2017-12-11 14:40 ` Gerd Stolpmann
2017-12-11 16:10 ` Ian Zimmerman
2017-12-11 16:47 ` Viet Le
2017-12-11 17:10 ` Yotam Barnoy
2017-12-11 18:56 ` Robert Muller
2017-12-11 19:23 ` Yawar Amin
2017-12-11 21:10 ` Marshall
2017-12-11 17:29 ` Yawar Amin
2017-12-11 17:59 ` Ian Zimmerman
2017-12-11 18:30 ` Gerd Stolpmann
2017-12-13 8:22 ` Sebastien Ferre
2017-12-13 9:26 ` Evgeny Khramtsov
2017-12-13 10:37 ` David Allsopp
2017-12-13 16:38 ` Marshall
2017-12-13 16:44 ` Yawar Amin
2017-12-13 17:20 ` David Allsopp
2017-12-13 17:51 ` Yawar Amin
2017-12-13 17:39 ` Hendrik Boom
2017-12-13 17:55 ` Robert Muller
2017-12-13 18:19 ` Viet Le
2017-12-13 19:29 ` Yawar Amin
2017-12-13 8:55 ` Nicolas Boulay
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=tencent_328F87040D5AB8198995C2DD09291F3D2C0A@qq.com \
--to=bob.hongbo.zhang@foxmail.com \
--cc=caml-list@inria.fr \
--cc=xramtsov@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