[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-error

From: Noam Postavsky
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

On Sun, Jun 25, 2017 at 3:34 PM, Stefan Monnier
<address@hidden> 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))

reply via email to

[Prev in Thread] Current Thread [Next in Thread]