From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: The poor state of documentation of pcase like things. Date: Sat, 2 Jan 2016 18:49:45 -0800 (PST) Message-ID: <83826ba7-d456-4cce-a3e4-af66f97212f2@default> References: <20151216202605.GA3752@acm.fritz.box> <87io3m60bq.fsf@web.de> <877fk1nnk0.fsf@web.de> <8760zlue3j.fsf@gmail.com> <87vb7kajgv.fsf@web.de> <83y4c9ag06.fsf@gnu.org> <87bn95m9eg.fsf@fencepost.gnu.org> <5686CDFB.2010105@dancol.org> <83fuygcs5g.fsf@gnu.org> <56886E32.70305@yandex.ru> <56887798.20208@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1451789421 10281 80.91.229.3 (3 Jan 2016 02:50:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Jan 2016 02:50:21 +0000 (UTC) Cc: michael_heerdegen@web.de, Eli Zaretskii , Daniel Colascione , dak@gnu.org, emacs-devel@gnu.org To: Dmitry Gutov , Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 03 03:50:08 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aFYk9-0004P4-4J for ged-emacs-devel@m.gmane.org; Sun, 03 Jan 2016 03:50:05 +0100 Original-Received: from localhost ([::1]:40328 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFYk8-0008WA-CS for ged-emacs-devel@m.gmane.org; Sat, 02 Jan 2016 21:50:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFYk4-0008Vs-U9 for emacs-devel@gnu.org; Sat, 02 Jan 2016 21:50:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFYk3-0006mL-Vr for emacs-devel@gnu.org; Sat, 02 Jan 2016 21:50:00 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:22065) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFYjy-0006kN-68; Sat, 02 Jan 2016 21:49:54 -0500 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u032nlTm010847 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 3 Jan 2016 02:49:47 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.13.8/8.13.8) with ESMTP id u032nlig002705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 3 Jan 2016 02:49:47 GMT Original-Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0122.oracle.com (8.13.8/8.13.8) with ESMTP id u032nkni010243; Sun, 3 Jan 2016 02:49:46 GMT In-Reply-To: <56887798.20208@yandex.ru> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197401 Archived-At: > cl-case is more restricted, yes, but I thought this discussion was about > how pcase is worse than cond. I don't think so. To me, this discussion is about whether to use `pcase': * Only when it really offers something, * All the time, everywhere, * Or something in between (what?). > > I kinda liked pcase at first, but the more I see of the pcase language, > > the more sceptical I get. I'm beginning to wonder whether the whole > > thing is a misfeature that should be replaced with several separate > > operators. >=20 > You mean pattern matching? A lot of language and library designers would > disagree with you. Decomposition pattern-matching. Use it when it helps. Literal "pattern" matching does not require `pcase'. Should `pcase' be used for such mundane cases anyway, since it can be? That's the question that I think is being discussed. Whether wholesale replacement of `cond', `case', `if', etc. by `pcase' is a good idea, just because it could do the job.