From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: emacs-26 8f18d12: Improve documentation of decoding into a unibyte buffer Date: Wed, 29 May 2019 15:50:16 -0400 Message-ID: References: <20190525191039.14136.23307@vcs0.savannah.gnu.org> <20190525191040.CCD6C207F5@vcs0.savannah.gnu.org> <83v9xv2649.fsf@gnu.org> <83imtv1fbf.fsf@gnu.org> <7F0B61E6-C0CA-449B-B432-095569589168@gnu.org> <83y32qzk9b.fsf@gnu.org> <83pno2za3d.fsf@gnu.org> <83blzmyo5h.fsf@gnu.org> <83muj5xgw9.fsf@gnu.org> <83k1e9xekl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="62490"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 29 21:51:05 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hW4bJ-000G4d-0i for ged-emacs-devel@m.gmane.org; Wed, 29 May 2019 21:51:05 +0200 Original-Received: from localhost ([127.0.0.1]:59845 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hW4bI-0006U2-1a for ged-emacs-devel@m.gmane.org; Wed, 29 May 2019 15:51:04 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:46114) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hW4ag-0006Pw-Jm for emacs-devel@gnu.org; Wed, 29 May 2019 15:50:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hW4af-0008Vh-Oq for emacs-devel@gnu.org; Wed, 29 May 2019 15:50:26 -0400 Original-Received: from [195.159.176.226] (port=58260 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hW4ad-0008Ri-Pv for emacs-devel@gnu.org; Wed, 29 May 2019 15:50:24 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hW4ab-000FG8-QD for emacs-devel@gnu.org; Wed, 29 May 2019 21:50:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:eeqpQhV8gqkONDVlBE1n0A2SlBg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237162 Archived-At: > I'm okay with enabling such checks in an Emacs configured with > '--enable-checking', but not in the production version. The main > purpose of a released Emacs is not to expose bugs, it's to allow users > do whatever they need to do in Emacs, even if it means tolerating some > bugs. Yes, as mentioned the default would be nil: there's no point signaling such errors to an end-user that hasn't specifically asked for such sanity checks. I hadn't (and still haven't) considered enabling those checks when --enable-checking is specified: it might turn out too many false positives currently. But I'll keep it in mind. Stefan