From: Noam Postavsky <npostavs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340)
Date: Wed, 28 Jun 2017 22:04:06 -0400 [thread overview]
Message-ID: <CAM-tV-_mn10miBiU7QafwXMZ6opRBi_dXOfxSz9JR1JcJ13_8w@mail.gmail.com> (raw)
In-Reply-To: <jwvd19rc18h.fsf-monnier+emacsdiffs@gnu.org>
On Sun, Jun 25, 2017 at 3:34 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> I agree that it's not really clear, but when you look at the doc of
> proclaim and compare it to that of declaim it seems clear what is the
> intention: one is meant to be "runtime only" (which is why it evaluates
> its argument and is just a normal function) while the other is designed
> such that it can be used at compile-time and only affects the
> compilation of the current file (although the doc allows the
> implementation to be less careful and let the effect "leak").
Sounds reasonable, so should it be just this?
(defmacro cl-declaim (&rest specs)
"Like `cl-proclaim', but takes any number of unevaluated, unquoted arguments.
Furthermore, the declarations are registered at compile-time."
(mapc #'cl-proclaim spec))
next prev parent reply other threads:[~2017-06-29 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170624141528.514.4459@vcs0.savannah.gnu.org>
[not found] ` <20170624141530.443C5210EB@vcs0.savannah.gnu.org>
2017-06-24 14:26 ` [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340) Stefan Monnier
2017-06-24 14:36 ` Noam Postavsky
2017-06-25 19:34 ` Stefan Monnier
2017-06-29 2:04 ` Noam Postavsky [this message]
2017-06-29 11:46 ` Stefan Monnier
2017-06-29 19:25 ` Johan Bockgård
2017-06-29 19:46 ` Noam Postavsky
2017-06-29 20:09 ` Johan Bockgård
2017-06-29 20:49 ` Stefan Monnier
2017-06-29 22:11 ` Johan Bockgård
2017-06-30 6:06 ` Stefan Monnier
2017-07-01 8:59 ` Johan Bockgård
2017-07-01 14:35 ` Stefan Monnier
2017-06-29 20:52 ` Stefan Monnier
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=CAM-tV-_mn10miBiU7QafwXMZ6opRBi_dXOfxSz9JR1JcJ13_8w@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.