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

From: Emanuel Berg <[email-masked]>
Date: Mon, 27 Nov 2017 03:49:42 +0100

Michael Heerdegen wrote:

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

It sure send mixed signals and as it stands one
gets the impression what you should do is find
ways of silencing warnings, instead of
improving the code so there is nothing to warn
about to begin with.

-- 
underground experts united
http://user.it.uu.se/~embe8573