Re: policy, recommendations regarding `cl-*'

[Michael Welsh Duggan]

Stefan Monnier <address@hidden> writes:

>>>> On a related note, am I understanding right that functions
>>>> and macros from cl-macs.el will *not* trigger warnings?
>>> Depends what kind of warning and in which circumstance.
>> I have a test.el file with just this:
>>   (eval-when-compile (require 'cl))
>>   (cl-position '1 '(0 1 2 3))
>>   (cl-defsubst test () (message "blah"))
>
> There's a bug: at run time, CL will not be loaded, so cl-position
> won't exist.
> For cl-defsubst, that's not a problem, because it gets macroexpanded
> away during compilation, so it's not needed at run-time.
>
> IOW if you use CL functions, you need (require 'cl-lib) without wrapping
> it in eval-when-compile.

I use cl-delete-if in my .emacs.el file.  I have (require 'cl-lib) near
the top.  However, when I compile this, I still get warnings:

In add-unique:
.emacs.el:31:63:Warning: function `cl-delete-if' from cl package called at
    runtime

In md5i-save-undo-information:
.emacs.el:353:34:Warning: function `cl-remove-if' from cl package called at
    runtime

I thought that when using the renamed functions there weren't supposed
to be any warnings generated?

-- 
Michael Welsh Duggan
(address@hidden)