Re: Fixing compilation and byte-compilation warnings before 25.1

[Michael Heerdegen]

daniel sutton <address@hidden> writes:

> Ah thank you. Someone responded and made a new thread and were super
> helpful as well. It seems like this warning needs to go to new
> consumers but not in the core. Would it be appropriate for the declare
> statement to somehow tell the compiler that we are in the core and
> therefore to suppress warnings of this type?

I don't think that suppressing blindly all warnings of any particular
type is a good idea.  Some of them might indicate problems.

> One suggestion was to add the recursive call into a (with-no-warnings
> ...) call, but this could get tedious and invasive.

Why not just leave this one particular warning?  It reminds us we still
have something to change there in the future.


Michael.