bug#29462: 24.4; eval-when-compile won't mute warning as says in info doc

[Michael Heerdegen]

Emanuel Berg <moasen@zoho.com> writes:

> In (info "(elisp) Warning Tips"), it says
>
>    * If you use many functions and variables
>      from a certain file, you can add
>      a ‘require’ for that package to avoid
>      compilation warnings for them.
>      For instance,
>
>           (eval-when-compile
>             (require 'foo))

Thanks for the report.

I find this whole sentence confusing and misleading in general.  The
main purpose of `require' is not to silence warnings, and calling it is
very often something needed, not only something one "can" do.


Michael.