From: Alain Frisch <alain.frisch@lexifi.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: oleg@okmij.org, Jun Furuse <jun.furuse@gmail.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do,
Date: Mon, 19 Jan 2015 10:40:35 +0100 [thread overview]
Message-ID: <54BCD113.70309@lexifi.com> (raw)
In-Reply-To: <CAPFanBF4n2C8nRn9aDuWRLpnN04xxiTKYYPYmcr-Ar=L_tgVMA@mail.gmail.com>
On 01/19/2015 10:06 AM, Gabriel Scherer wrote:
> (On the other hand, the remark that the existing uses of keyword-bang in
> the language, namely (method!) and (open!), could now be represented as
> annotations is fairly reasonable.)
Indeed, these ! markers only affect warnings, and don't change the
static or dynamic semantics otherwise, so I wouldn't be shocked if they
were represented internally with attributes. Unless perhaps if we
consider that forcing users to mark method overrides, as in many other
class-based OO languages, should become part of the language definition
(i.e. turned into a strong error at some point).
-- Alain
next prev parent reply other threads:[~2015-01-19 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:23 [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern guards and monadic comprehension Jun Furuse
2015-01-14 8:40 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern oleg
2015-01-18 14:47 ` Jun Furuse
2015-01-19 7:33 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, oleg
2015-01-19 8:34 ` Alain Frisch
2015-01-19 9:06 ` Gabriel Scherer
2015-01-19 9:40 ` Alain Frisch [this message]
2015-01-19 16:10 ` Jeremy Yallop
2015-01-19 8:56 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern Alain Frisch
2015-01-19 21:52 ` Drup
2015-01-20 3:53 ` Jun Furuse
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=54BCD113.70309@lexifi.com \
--to=alain.frisch@lexifi.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=jun.furuse@gmail.com \
--cc=oleg@okmij.org \
/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).