Re: Has eval-and-compile changed in emacs 27?

[Leo Liu]

On 2021-02-25 17:29 -0500, Stefan Monnier wrote:
> That one's easy: the way the warning works is that when we process
> a `eval-when-compile` we look at the `load-history` to see the functions
> that have been defined during execution of its body, and then we remember
> those as "only available now but maybe not at runtime".
>
> If that loaded `cl-lib`, then a subsequent (require 'cl-lib) will be
> a no-op and won't "unremember" the corresponding functions.

This sounds like nightmare :(

Is this new in Emacs 27? What prompted the change?

I think when managing dependencies I want to be able to look locally at
what I put in a elisp file and be done with it.

The new behaviour means I also need to chase dependencies and their
dependencies...

Another point is subsequent (require 'cl-lib) provides stronger
guarantee but is ignored which produces spurious warnings.