bug#46617: 28.0.50; nativecomp: native compile cache is not invalidated when file is re-byte compiled and changes

[Aaron Jensen <aaronjensen@gmail.com>]

On Sun, Mar 21, 2021 at 3:54 PM Andrea Corallo <akrl@sdf.org> wrote:
>
> Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>
> Okay I've added `comp-lookup-eln' son now the user can search if a
> certain .eln is in reach in `comp-eln-load-path' for a given .el.
>
> So now one can use the following to force a native load.
>
> (load (comp-lookup-eln ".../foo.el"))

Okay, and that would return nil if it's not native compiled, which
would be their cue to native compile it, yes? That's nice to be able
to force load it.

Without doing the modification date stuff you mentioned or purge
before byte compile, native compilation ends up having to be a concern
of anything that's doing byte compiling, which is unfortunate. Ideally
Straight.el could just change to doing a (load "foo") after the
explicit byte compile and get the automatic async native compilation.
They could also do a delete file if the result of comp-lookup-eln
exists, prior to or just after byte compiling, then at least they
won't have to native compile synchronously.

Thanks,

Aaron