From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: combining cond and let, to replace pcase. Date: Sun, 19 Nov 2023 13:43:07 +0200 Message-ID: <831qcmklys.fsf@gnu.org> References: <878r6u3s7f.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27869"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, sbaugh@janestreet.com, emacs-devel@gnu.org To: Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 19 12:44:29 2023 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 1r4gE0-000758-Q4 for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Nov 2023 12:44:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r4gD8-0007fb-No; Sun, 19 Nov 2023 06:43:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r4gD7-0007fT-8U for emacs-devel@gnu.org; Sun, 19 Nov 2023 06:43:33 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r4gD6-0006JD-0T; Sun, 19 Nov 2023 06:43:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=yMEay18RmozOnASrTYax1VTtOANC01et8QYNXypsUfQ=; b=ToEoIyllVQXg cOiw2dx1AvNTo85GTUGBsvRrvgbzdcbLONgw0/UILoRa2cVPqjKjUn3fehZxrLHUMmYvhnC4a9a7D 9k8qrDEFJG4I4b1CJjrNLaAoYZ9iQqIzxB10U3HTN2uLgFNxLYPN7gilf5FzS6oRrDaoNIyD+NO5a k7tAX0VxP2vnyMD5bOhakgJN7XS4yQpSy7poiEdNsi5ZX8cnd+D4EHNPYG50rwG4q73ef6s6vJ0YX oDRgnZ/A9Yl6Q0mnO3yS2dasWB8Rx7sGqxx+9MMbsZs78pmqDkWdOciQ0Ng7tZnxOKKl+neiTxSzC 7KmHLzfIc6Vo4py6TROeDg==; In-Reply-To: <878r6u3s7f.fsf@web.de> (message from Michael Heerdegen on Sun, 19 Nov 2023 12:20:20 +0100) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312964 Archived-At: > From: Michael Heerdegen > Cc: Spencer Baugh , emacs-devel@gnu.org > Date: Sun, 19 Nov 2023 12:20:20 +0100 > > To sum up, I question your premise of this discussion. Don't. It's a real issue. Maybe not for you, but for some others. No one in their right mind would assume that Richard has "a problem understanding the abstract approach". Just look at which pieces of software he wrote and the various DSLs he designed while at that. So when Richard, of all the people, tells us there's a problem, I suggest that we listen, especially since a few other veteran Emacs developers, who are not unfamiliar with Emacs Lisp and its subtleties, tell something similar if not identical. It could be that pcase is not a problem for you, but that's not what this discussion is about. When on several occasions I told you that some piece of documentation is clear for me, you still insisted for it to be fixed because it wasn't clear for you, and you were right. Because the documentation I write is not for me, it's for others. > In my opinion `pcase' comes very close to the optimal solution for > its task. The same is true for regular expressions. But we still have rx, and some people really prefer it. Maybe this imperfect analogy will help you understand the issue with pcase.