From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let Date: Fri, 19 Jan 2018 15:40:22 -0500 Message-ID: References: <87zi5njxvd.fsf@cassou.me> <87h8rv1m7p.fsf@petton.fr> <87o9m0u4zz.fsf@cassou.me> <83fu71tx1p.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1516394364 17998 195.159.176.226 (19 Jan 2018 20:39:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 19 Jan 2018 20:39:24 +0000 (UTC) Cc: Damien Cassou , 30039@debbugs.gnu.org, Nicolas Petton To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jan 19 21:39:19 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ecdRP-0003vW-NF for geb-bug-gnu-emacs@m.gmane.org; Fri, 19 Jan 2018 21:39:11 +0100 Original-Received: from localhost ([::1]:43720 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecdTM-0003mQ-1r for geb-bug-gnu-emacs@m.gmane.org; Fri, 19 Jan 2018 15:41:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecdTF-0003le-DR for bug-gnu-emacs@gnu.org; Fri, 19 Jan 2018 15:41:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ecdTC-00047G-BT for bug-gnu-emacs@gnu.org; Fri, 19 Jan 2018 15:41:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:55617) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ecdTC-000478-7Q for bug-gnu-emacs@gnu.org; Fri, 19 Jan 2018 15:41:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ecdTB-0005bm-Mx for bug-gnu-emacs@gnu.org; Fri, 19 Jan 2018 15:41:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 19 Jan 2018 20:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30039 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30039-submit@debbugs.gnu.org id=B30039.151639443221513 (code B ref 30039); Fri, 19 Jan 2018 20:41:01 +0000 Original-Received: (at 30039) by debbugs.gnu.org; 19 Jan 2018 20:40:32 +0000 Original-Received: from localhost ([127.0.0.1]:35281 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ecdSi-0005au-4k for submit@debbugs.gnu.org; Fri, 19 Jan 2018 15:40:32 -0500 Original-Received: from mail-wr0-f171.google.com ([209.85.128.171]:36860) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ecdSe-0005ag-Oc for 30039@debbugs.gnu.org; Fri, 19 Jan 2018 15:40:29 -0500 Original-Received: by mail-wr0-f171.google.com with SMTP id d9so2663024wre.3 for <30039@debbugs.gnu.org>; Fri, 19 Jan 2018 12:40:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=MwX0WKKgAeS2uLJEXQFoR2BZavFQTNjHiu4aGOvwIjI=; b=ZealKJ+8lK7QqqjtOkmOCoFHO7lt4a5RT/dIkbVlMmaoP3IiHJnnomCkYlKKa9rOIQ PyYmz3mNgrZIn5NWt/k5dUFIxOn7PMGeYKSeddp/Aa4BUQnFQR+xKGeWzaay3ZQOlV6D ZYFXdjPhWm9FUChQtrlSW8MxKb7zDqDlIodIfEK70O3tpLvyfrOnZfcIBFXg9WPgasGH MGRUhaiPPEnJ5uD12zCjk4gxiWEb7oQDQf1l7k2PdsmVV12c5869McuDES5bvCrYp1on wkdRYDAKzMqvvko940xRuLHiYArRJzwkMOko/m0B7B1+iuJn8sUDHA8UIKrWAdc5MBat cVFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=MwX0WKKgAeS2uLJEXQFoR2BZavFQTNjHiu4aGOvwIjI=; b=Vkt2nl2vXZCNj3MXUHfK9VFf6g6AdsSQsYnFQwZM6bFHLFOVclNjFRwLKtwox8Kxup WhYjmZqdz0EUZDzW2u4MVPsrRrRoLciBiWaqipuGTbMwzmDdt/TKnMbBQ7WvXlLJySBB LrK6Z2S8IP2CZUXbMPMkfnujbVAhgxXy+vohNyLlkUQt8rZM6NwdwVHNQ2hIEMhKoTdh 5Z6W9wwHbyuPuHpVN5if1hZ7HfMt/ZHf0S15Rq1Gk6qHOe57+PArfebBuChkjpHjx8Pq AkPbhMRu29ccP3hv53ZBvEshmbNHd+ASFVOqzUKm+aThoBrA/bm6clUJxGVRAgyCUcIi Id1Q== X-Gm-Message-State: AKwxyte03SZvEz0ne8Q6EzNoEdPsB6dK3tZdqqMa/42/ZlMdNbVn97DU 0O4DVWwXWykg9c8JxlcI4JDqwkLfQFy2/KPSyHo= X-Google-Smtp-Source: ACJfBouSYC+DGOCZekE5+pa9gYvKy/ahpq55IOiS3no3oT8RXbj/8+k+jwRqzFwjUpYMYK+1B3mZjokLoGWt/8A95Gc= X-Received: by 10.223.182.65 with SMTP id i1mr3033927wre.92.1516394423133; Fri, 19 Jan 2018 12:40:23 -0800 (PST) Original-Received: by 10.223.182.77 with HTTP; Fri, 19 Jan 2018 12:40:22 -0800 (PST) In-Reply-To: <83fu71tx1p.fsf@gnu.org> X-Google-Sender-Auth: Dn9gdLdqY526xAT9Bd_z8ipys-A X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:142305 Archived-At: On Fri, Jan 19, 2018 at 3:26 PM, Eli Zaretskii wrote: >> From: Noam Postavsky >> Date: Fri, 19 Jan 2018 15:00:30 -0500 >> Cc: 30039@debbugs.gnu.org, Nicolas Petton >> >> Here's a finished version of the patch. Eli, is it okay for emacs-26? > > Why is this new feature is urgent or important enough to have it in > Emacs 26? It's urgent, because it has to be in 26.1 in order to solve the problem in the OP. More generally, if we introduce the feature in 26.1 in can be useful for suppressing warnings from 26.1 and up, whereas if we delay it until 27, then it won't be helpful for things marked obsolete in 26.1. So the timing of when we add it directly affects the usefulness. On the other hand, it's maybe not that important, as the problem is only a warning, and there are other ways of suppressing it (e.g., what I suggested in #11).