Re: policy, recommendations regarding `cl-*'

[Bastien]

Stefan Monnier <address@hidden> writes:

> 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.

That's perfectly clear, thanks.

-- 
 Bastien