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: Sat, 24 Jun 2017 10:36:39 -0400 [thread overview]
Message-ID: <CAM-tV-_OuF+5-xu6nbTZrG5==jPWz_VPq213njpZjJ+PiMqmXA@mail.gmail.com> (raw)
In-Reply-To: <jwv8tkhbh3a.fsf-monnier+emacsdiffs@gnu.org>
On Sat, Jun 24, 2017 at 10:26 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> * lisp/emacs-lisp/eieio-core.el: Confine `cl-declaim' calls to compile
>> time.
> [...]
>> - (cl-declaim (optimize (safety 0)))
>> + (eval-when-compile (cl-declaim (optimize (safety 0))))
>
> I'd argue that cl-declaim should have no effect when interpreted, just
> like (defvar foo). At least, that's how I understand the difference
> between CommonLisp proclaim and declaim.
https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node104.html (bottom of
page) says:
declaim {decl-spec}*
This macro is syntactically like declare and semantically like
proclaim. It is an executable form and may be used anywhere
proclaim may be called. However, each decl-spec is not evaluated.
If a call to this macro appears at top level in a file being
processed by the file compiler, the proclamations are also made at
compile time.
Which suggests that declaim's effects are a superset of proclaim's
effects. But then it also says
As with other defining macros, it is unspecified whether or not
the compile-time side effects of a declaim persist after the file
has been compiled
So I guess we could drop the effects at runtime?
next prev parent reply other threads:[~2017-06-24 14:36 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 [this message]
2017-06-25 19:34 ` Stefan Monnier
2017-06-29 2:04 ` Noam Postavsky
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-_OuF+5-xu6nbTZrG5==jPWz_VPq213njpZjJ+PiMqmXA@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.