Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340)

[Noam Postavsky <npostavs@gmail.com>]

On Thu, Jun 29, 2017 at 3:25 PM, Johan Bockgård <bojohan@gnu.org> wrote:

> This is wrong. declaim has run-time effects, just like defvar etc. The
> compile-time side effect is that it ALSO affects the compilation of the
> remainder of the current file.
>
> http://www.lispworks.com/documentation/HyperSpec/Body/03_bcaa.htm

So you don't think this statement allows to omit run-time effects?

    It is not specified whether definitions made available in the
    compilation environment are available in the evaluation
    environment, nor is it specified whether they are available in
    subsequent compilation units or subsequent invocations of the
    compiler.

PS my earlier definition of cl-declaim had 2 bugs in it, I should have written

(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 specs)
  nil)