Re: Zero byte-compiler warnings in the test suite

[Stefan Kangas]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> The test expects the error to be signal'd at run time whereas the
> compiler macro prefers to signal the error right away.
> As a bias observer, I'd suggest to fix the test rather than the compiler
> macro ;-)

How do we usually test compiler macros?  I guess we should create a
separate file and try to byte-compile it?

Or should we just disable the test in non-interactive sessions?