Re: Native compilation on as default?

[Eli Zaretskii]

> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
> Cc: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
>  emacs-devel@gnu.org
> Date: Thu, 26 Oct 2023 05:47:15 +0200
> 
> Andrea Corallo <acorallo@gnu.org> writes:
> 
> > As asynchronous native compilation always starts from a pristine
> > environment, it is more sensitive to such omissions, and might be
> > unable to compile such Lisp source files correctly.
> > "
> >
> > Essentially if in Emacs one has for any reason the definition of the
> > macro loaded before invoking the byte-compiler, this will not complain
> > even if the require is missing.
> 
> Does this mean that previously working Emacs packages or setups may be
> broken with native compilation?

I don't see how the text above could be interpreted to mean that some
package will be "broken".  A warning about some symbol being unknown,
or its function slot being void, never prevents Emacs from emitting
valid code, which will DTRT if that symbol or function are known at
run time.

This whole sub-thread is about _warnings_ emitted by async
compilation, which annoy some people, that's all.  Nothing will ever
become "broken" due to a warning, unless it was already broken to
begin with.

> Or only that such packages would not get the speed-boost from native
> compilation?

Not even that.  Only if the native compilation _errors_out_, you will
get the lack of speed-boost, because the .eln file will not be
written.