bug#38072: when `byte-compile-file' finds out that a file is `no-byte-compile', it ignores `load' parameter

[Eli Zaretskii <eliz@gnu.org>]

> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 5 Sep 2020 00:30:38 +0000
> Cc: 38072@debbugs.gnu.org
> 
>     Compile a file of Lisp code named FILENAME into a file of byte code.
>     The output file’s name is generated by passing FILENAME to the
>     function ‘byte-compile-dest-file’ (which see).
>     With prefix arg (noninteractively: 2nd arg), LOAD the file after compiling.
>                                                                ^^^^^^^^^^^^^^^
> 
> So should we load the file if we did not compile the file?  I'm thinking
> yes, and I don't see what it could hurt to change it to load the file.
> If the user uses a prefix arg or the LOAD argument from Lisp, surely
> that was the intention.
> 
> But on the other hand the text above seems deliberate, somehow?  (And
> AFAICT the behavior has been not to load the file since pretty much
> forever, possibly since byte-compilation was first added.)

I'm indeed bothered by backward incompatibility of such a change.
Paul expected the file to be loaded unconditionally, but how do we
know someone else isn't expecting the opposite in this case?  Also, do
we want the same behavior in the interactive case?

At the very least, if we decide to install this, the change in
behavior should be in NEWS.

Stefan, any comments on this?