bug#72313: 31.0.50; Warning about cl-member possibly being undefined when using cl-pushnew

[Stefan Monnier]

> So the conclusion is to simply (require 'cl-lib) instead of
> (eval-when-compile (require 'cl-lib))?  But how can the byte-compiler
> conclude that cl-member might not be defined at runtime given that it's
> an autoloaded function?

It's autoloaded from `cl-seq` when `cl-lib` is loaded.
It's not autoloaded at startup.

> Addon question: should a package list cl-lib in Package-Requires if it
> already requires an Emacs version where a good-enough cl-lib is included
> anyway?

I can't see any reason to do that, no.


        Stefan