From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: cl-lib warnings Date: Sat, 24 Dec 2022 10:33:44 +0000 Message-ID: <87ili1f5vb.fsf@posteo.net> References: <86o7s3lsnx.fsf@mail.linkov.net> <86bknx8783.fsf@mail.linkov.net> <837cylapt4.fsf@gnu.org> <83wn6kamwr.fsf@gnu.org> <83len0aldq.fsf@gnu.org> <83k02kadbv.fsf@gnu.org> <83a63fap35.fsf@gnu.org> <83bknu8tmo.fsf@gnu.org> <18E95AC5-1FFC-4025-B804-7D70DDB1BD75@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="37150"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , Eli Zaretskii , Juanma Barranquero , Juri Linkov , Stefan Monnier , emacs-devel To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 24 11:34:18 2022 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 1p91r7-0009VH-RW for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Dec 2022 11:34:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p91qf-00068h-KK; Sat, 24 Dec 2022 05:33:49 -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 1p91qe-00068H-GK for emacs-devel@gnu.org; Sat, 24 Dec 2022 05:33:48 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p91qc-0006HC-Ny for emacs-devel@gnu.org; Sat, 24 Dec 2022 05:33:48 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id B60A32400E3 for ; Sat, 24 Dec 2022 11:33:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1671878022; bh=fv8cuEqhwk0G2yhA/5CDtahVPTMdUpeqXlzt3vqoGsk=; h=From:To:Cc:Subject:Date:From; b=LODOZp82VaKh2/yvHDiQNxZCuN944/oEXpDapmyaqE/+XtTszKSsLlWPUZ1PraiuC rhIasSm1nlJXty6QrnxrzKbZUX4zAIndngx85gzsNIfVre3GmzmcRNuMVjgrfQ8Uvm I7rlVr7RvIATjjovXsN7Vt6I1ZivUe4tKFjugEd2cJ0qspQvnrLSOlOGQH+igvXo8U E03+e8b8HE7ShVM/WV1bHF5WySwHXaMlj0CNWkVLQLLTsIe1nMC1VqfEWXBDr8Lvol YlcIY0PdCJYIPzFNrFWB9bnlUR753YxGTy4t5oUkczFi4p/GwzcvCwOImlsTMRAd0j zuq49fq2L0t8w== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NfL4P0dZPz9rxM; Sat, 24 Dec 2022 11:33:38 +0100 (CET) In-Reply-To: (=?utf-8?Q?=22Jo=C3=A3o_T=C3=A1vora=22's?= message of "Sat, 24 Dec 2022 00:26:06 +0000") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301834 Archived-At: Jo=C3=A3o T=C3=A1vora writes: > On Fri, Dec 23, 2022, 23:42 Yuan Fu wrote: > >> Yes, cl-loop is one of the worst offenders in my eyes. If I want to >> > use Fortran or C, I will use Fortran or C; I don't want to see Fortran >> > for-loops in Emacs Lisp. >> >> Darn it! I loved cl-loop :-) I=E2=80=99ll curb my use of cl-loop in Emac= s codebase. >> > > As a data point, some of us are, like you, highly appreciative of cl-loop, > and cannot see anything remotely approaching its versatility in other > programming languages. I don't know what its detractors recommend for > iterating over a plist, to give just one example. I would guess a custom function, say `plist-map' along the lines of `maphash'. I am kind of surprised to see that this doesn't exist, but according to my intuition of property lists, they are not meant to be iterated. While writing this, I also just realise this exists in the "map" package. (map-do (lambda (key val) (message "Key %s, Value %s" key val)) '(:one 1 :two 2 :three 3))