unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: native-comp-async-report-warnings-errors default value
Date: Mon, 06 Dec 2021 22:26:45 +0200	[thread overview]
Message-ID: <83v901zdh6.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=NouBfRHwBg4KhkXZCB5oE9k=-qkMNjE2QwUzxFcFqJw@mail.gmail.com> (message from Stefan Kangas on Mon, 6 Dec 2021 21:11:21 +0100)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Mon, 6 Dec 2021 21:11:21 +0100
> Cc: rpluim@gmail.com, emacs-devel@gnu.org
> 
> > Emacs knows when it loads the init file.  We could disable warnings
> > during that load, perhaps.
> 
> That works until you require some package from there, I think.  In any
> case, that would need someone to step up to write that code, and it
> sounds a whole deal more complicated than just flipping
> native-comp-async-report-warnings-errors to nil.

Then flip it.  For yourself.  Why decide for all the others?

I'd rather sustain a barrage of annoyed people who think these
warnings are gratuitous than explain to someone why Emacs decided to
shut up these warnings by default and thus prevented him/her from
seeing some warning which, if seen in time, could avoid a crash or
some other catastrophic result.

Native compilation is still in its diapers.  We learn about new
aspects and potential issues with it almost every day.  Sweeping
warnings under the carpet in this situation makes very little sense to
me.  It's our minimal safety net.

But if "by popular demand" and other pressure, you will decide to
disable the warnings nonetheless, I won't mount the barricades.  My
opinion about this is unchanged, but feel free to disregard it.



  reply	other threads:[~2021-12-06 20:26 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 11:23 native-comp-async-report-warnings-errors default value Robert Pluim
2021-10-14 11:30 ` Eli Zaretskii
2021-10-14 11:43   ` Robert Pluim
2021-10-14 11:52     ` Eli Zaretskii
2021-10-14 14:48       ` Robert Pluim
2021-10-14 15:57         ` Eli Zaretskii
2021-10-14 16:42           ` Lars Ingebrigtsen
2021-10-14 16:47             ` Eli Zaretskii
2021-10-15  8:51           ` Robert Pluim
2021-10-14 12:07     ` Stefan Kangas
2021-10-14 12:12       ` Eli Zaretskii
2021-12-02 17:03     ` Stefan Kangas
2021-12-02 17:10       ` Lars Ingebrigtsen
2021-12-02 17:14         ` Andrea Corallo
2021-12-02 21:15           ` T.V Raman
2021-12-02 18:23       ` Eli Zaretskii
2021-12-02 19:27         ` Stefan Kangas
2021-12-02 19:42           ` Eli Zaretskii
2021-12-06 20:11             ` Stefan Kangas
2021-12-06 20:26               ` Eli Zaretskii [this message]
2021-12-07  7:51                 ` Lars Ingebrigtsen
2021-12-07  9:37                   ` Andrea Corallo
2021-12-07  9:42                     ` Robert Pluim
2021-12-07  9:54                       ` Andrea Corallo
2021-12-07 12:38                         ` Robert Pluim
2021-12-07 14:28                           ` Eli Zaretskii
2021-12-07 16:54                             ` Robert Pluim
2021-12-07 17:16                               ` Eli Zaretskii
2021-12-08  9:19                                 ` Robert Pluim
2021-12-08 13:23                                   ` Eli Zaretskii
2021-12-08 13:46                                     ` Andrea Corallo
2021-12-07 13:24                     ` Stefan Monnier
2021-12-07 14:05                       ` Andrea Corallo
2021-12-07 14:33                         ` Eli Zaretskii
2021-12-07 14:15                   ` Eli Zaretskii
2021-12-07 20:20                     ` Lars Ingebrigtsen
2021-12-17 18:14                 ` Stefan Kangas
2021-12-17 19:12                   ` Eli Zaretskii
2021-12-17 19:27                     ` Óscar Fuentes
2021-12-17 19:36                     ` Stefan Kangas
2021-12-17 20:07                       ` Stefan Kangas
2021-12-17 20:38                         ` Eli Zaretskii
2021-12-17 20:53                           ` Dmitry Gutov
2021-12-17 21:20                             ` Colin Baxter 😺
2021-12-17 22:01                             ` Ken Brown
2021-12-18  0:48                               ` Dmitry Gutov
2021-12-18 14:38                                 ` Ken Brown
2021-12-18 16:58                                   ` Óscar Fuentes
2021-12-18 20:51                                     ` Ken Brown
2021-12-17 22:10                             ` Rudolf Adamkovič
2021-12-17 21:10                           ` Stefan Kangas
2021-12-18  0:24                         ` Po Lu
2021-12-20  8:29                         ` Andrea Corallo
2021-12-24  1:01                           ` Dmitry Gutov
2021-12-24  1:34                             ` T.V Raman
2021-12-24  9:53                             ` Andrea Corallo
2021-12-25  0:05                               ` Dmitry Gutov
2021-12-25 10:53                                 ` Andrea Corallo
2021-12-28  1:59                                   ` Dmitry Gutov
2021-12-30  9:37                                     ` Andrea Corallo
2022-01-08  2:29                                       ` Dmitry Gutov
2021-12-02 21:14       ` T.V Raman
2021-12-03  6:50         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v901zdh6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=stefankangas@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).