Re: Merging native-comp and pgtk

[Andrea Corallo]

Stefan Kangas <stefankangas@gmail.com> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>
>>> The drawback is that we get compilation warnings pop up every now and
>>> then, which is arguably somewhat disruptive.  But this could be improved
>>> upon, I think.  For example, I'm not sure users need to see all warnings
>>> by default for installed packages even in the byte-compilation case.  We
>>> could perhaps have an option to enable these warnings for the genuine
>>> sticklers out there.  (I for one would definitely turn it on...)
>>
>> Hi Stefan,
>>
>> we have the `comp-async-report-warnings-errors' customize to control
>> this.
>
> Should that perhaps default to nil?  I'm not sure users typically need
> to see these warnings -- developers do.

In the past a lot of developers not seing these warnings on native-comp
got hit by this.

I think we touched on the reasons why hiding warnings on native-comp is
dangerous here <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44746#8>.

So yeah I agree with you normal users are not interested, but developers
should learn that this customize exists and set it to t, this is not
100% trivial.

Anyway I guess as every default the best value is very debatable :)

  Andrea