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: What's missing in ELisp that makes, people want to use cl-lib? Date: Fri, 03 Nov 2023 16:27:00 +0200 Message-ID: <83a5ru7w0b.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19208"; mail-complaints-to="usenet@ciao.gmane.io" Cc: paaguti@gmail.com, emacs-devel@gnu.org To: Gerd =?iso-8859-1?Q?M=F6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 03 15:27:56 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 1qyv9P-0004lo-RE for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Nov 2023 15:27:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qyv8b-0005Nl-Su; Fri, 03 Nov 2023 10:27:05 -0400 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 1qyv8a-0005Nc-TM for emacs-devel@gnu.org; Fri, 03 Nov 2023 10:27:04 -0400 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 1qyv8a-0004PA-KB; Fri, 03 Nov 2023 10:27:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=iNCmQ1Ij+pMhB4tc6YZDamctIPVOBjE8ITAQ64jND9M=; b=gN/C4ucnU4suo6ZICbix BkpOpvLkNAwgM2DS6ZVCAvHsvFYyDftUerB9t5AOuhyq4wvgCYznICp0y3knzLfpUZFOYIlTCKQfF Z3BIVPbJqRpKCCQJfLdmAYQyGoo8i3eeyQlRPtGxOETBcIYFJ5VwbuDk6hCoB8srzWHuGuvARc3y9 FJwiVzsdvS4R7ye8QrW3FKBfSQNudcFAQabTmqJdBUoDmO7DXW+JkwoBFQpYQvnrq6+0vThtmAZUV aSFG8TK5TrK4XBQIOb2RtnYoJxQIW91YApCZGw2e10bO5+6VvIzSfohBbWL3z9CodMOw0fh/icCod L4CcyVb922DK4g==; In-Reply-To: (message from Gerd =?iso-8859-1?Q?M=F6llmann?= on Fri, 03 Nov 2023 14:37:14 +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:312163 Archived-At: > From: Gerd Möllmann > Cc: emacs-devel > Date: Fri, 03 Nov 2023 14:37:14 +0100 > > The reason I will not use seq.el or map.el in the forseeable future is > quite simple: I haven't ever needed an abstraction over sequence types > using generic functions, and I never have CPU cycles to give away for > free. What prevents us from implementing in seq.el methods for specific types of sequences? AFAIU, the only reason we didn't is because no one has yet came up with important situations where the generics in seq.el are not performant enough.