From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: native-comp-async-report-warnings-errors default value Date: Tue, 07 Dec 2021 09:54:12 +0000 Message-ID: References: <87h7dj7su7.fsf@gmail.com> <83r1cnlu6y.fsf@gnu.org> <87czo77rx7.fsf@gmail.com> <837dcmamt2.fsf@gnu.org> <83v90694ka.fsf@gnu.org> <83v901zdh6.fsf@gnu.org> <8735n4hmyn.fsf@gnus.org> <878rwwhhu6.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26750"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , emacs-devel@gnu.org, Eli Zaretskii , Stefan Kangas To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 07 10:56:27 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1muXCx-0006fT-Ni for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 10:56:23 +0100 Original-Received: from localhost ([::1]:59420 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muXCw-0001wM-8U for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 04:56:22 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57516) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muXAw-00087R-Je for emacs-devel@gnu.org; Tue, 07 Dec 2021 04:54:18 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:56083) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muXAu-0008Qw-3J; Tue, 07 Dec 2021 04:54:18 -0500 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 1B79sC67021338 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 7 Dec 2021 09:54:13 GMT In-Reply-To: <878rwwhhu6.fsf@gmail.com> (Robert Pluim's message of "Tue, 07 Dec 2021 10:42:09 +0100") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:281233 Archived-At: Robert Pluim writes: >>>>>> On Tue, 07 Dec 2021 09:37:30 +0000, Andrea Corallo sa= id: > > Andrea> What is the problem with changing it after pretest is done? > > Andrea> In the Emacs world by definition there's no clear distinction= between > Andrea> users and developers, postponing the switch we maximize the p= robability > Andrea> that some user/developer fix some broken code no? > > Are there clear instructions somewhere mapping from the warnings to > the changes required in the 'broken code'? (I wouldn=CA=BCt call it 'brok= en' > if it works in current Emacs) The docstring of `native-comp-async-report-warnings-errors' itself mention the tipical reason of this and its classical fix. It might be mentioned elsewhere tho, not sure. Andrea