From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: elisp code to list interactive functions Date: Thu, 04 Nov 2021 16:20:43 -0400 Message-ID: References: <874k8sz67e.fsf@h-brs.de> <878ry4mf0u.fsf@gmail.com> <87h7crvoh5.fsf@gnus.org> <871r3vr83e.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28264"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Philipp Stephani , Robert Pluim , Alexander Asteroth , Emacs developers To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 04 21:22:09 2021 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 1mijFR-0007Aq-4a for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Nov 2021 21:22:09 +0100 Original-Received: from localhost ([::1]:36196 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mijFQ-0005vm-3L for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Nov 2021 16:22:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38292) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mijEQ-00059n-1a for emacs-devel@gnu.org; Thu, 04 Nov 2021 16:21:06 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:19079) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mijEL-0005Vm-TR for emacs-devel@gnu.org; Thu, 04 Nov 2021 16:21:04 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 2685E8065D; Thu, 4 Nov 2021 16:21:00 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 777F480011; Thu, 4 Nov 2021 16:20:58 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1636057258; bh=4j5CBj4DtFl9et8TGfPMaSlTinmX9qZPqk85ikqWmmc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=gAu26SWLOmteU999VLaTQhQX/FYHKSy1MMZzaAmBVgHJTCJouB8lFdLYTvtN4cTBU LNnx2PQ1Z32+IjzSef80djHH3DGysAbdekEM4OW8gvL5bfb7x5GXmt4mjNcVg8kjPt RT0N87N8yZm6nVhIR7gjUr+nDQG+9PZqg7I1fDKzQXKQsAbqWJ5N24jb+q4ozmXN0K ODJ6UbvRzBQkP5JOmtm46eLjZdRrZfnZkznZk4qKRFeVRbrfrTdZyV+1bk61UspsCm Aqppi10ZNv/sGjcdfIQevZ87V8wBI7k/oYFN6yRIwDHwV0PDmR4TTaiT+E+N62c3N2 AlIBGmwAGos1g== Original-Received: from alfajor (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 5A4B8120867; Thu, 4 Nov 2021 16:20:58 -0400 (EDT) In-Reply-To: <871r3vr83e.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 04 Nov 2021 21:15:01 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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" Xref: news.gmane.io gmane.emacs.devel:278719 Archived-At: Lars Ingebrigtsen [2021-11-04 21:15:01] wrote: > Stefan Monnier writes: >>> (seq-filter #'commandp obarray) >> Sweet: not only the code is shorter, but the returned value is much >> shorter as well ;-) > Win win! > I thought somebody had extended the seq functions to also work on these > thingies, but I guess not? Nope. I did provide a patch which introduced a separate type for obarrays, but it come with some rough corners, and in any case it introduces a backward incompatibility with fairly limited advantages, so it's not clear it's a good idea. But until such a thing is done, we can't reliably distinguish an obarray from a vector. This said, an obarray is fundamentally unordered, so it would be odd for `seq.el` to support it. Stefan