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: Distinguishing `consp` and `functionp` Date: Sat, 27 Jan 2024 09:41:48 -0500 Message-ID: References: <87o7d6kjfe.fsf@yahoo.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="3996"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 27 15:42:32 2024 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 1rTjtA-0000sG-Gn for ged-emacs-devel@m.gmane-mx.org; Sat, 27 Jan 2024 15:42:32 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rTjsb-0006pi-FA; Sat, 27 Jan 2024 09:41:57 -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 1rTjsZ-0006pV-OS for emacs-devel@gnu.org; Sat, 27 Jan 2024 09:41:55 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rTjsX-0002sW-DM for emacs-devel@gnu.org; Sat, 27 Jan 2024 09:41:55 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 42E80441502; Sat, 27 Jan 2024 09:41:51 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1706366509; bh=QlcHbtFix/YyaqNekfUw2cNJIO39SYpBvrgiimelGhY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=huTM6uZbLMPHD+1IQ5HK86sYoEMOVCs5TmGMDcOTOcP3sb0R6SB/2zg5NhZz5AHN1 mc8FuRWoDk7KTnyHel774c5IZePpK0gEHukU8QnG24ATFo5qYSd3ZqXo07nhrZ+7uy heLHeD79NxmidBNkDqdNzo+OW/LKGweE790/Xbo1yxP2MLo5//Yvcvc/hy6aXladky LfoK09+LQlVOwqfFH7kvtdk7O0tk2sfSUKwbXdMz+y3r7W6HkyX8lsx2XV094D/EgM UKrh3LRvh5qg9o4eMKJ96YxR3gUIa8PfHAQt9A4Qus5Ajm+jzsaHy73JvG/GDk08c0 dWNE6lT5nHHsg== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D41A14409A6; Sat, 27 Jan 2024 09:41:49 -0500 (EST) Original-Received: from pastel (unknown [45.72.206.68]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B2337120209; Sat, 27 Jan 2024 09:41:49 -0500 (EST) In-Reply-To: <87o7d6kjfe.fsf@yahoo.com> (Po Lu's message of "Sat, 27 Jan 2024 21:14:13 +0800") 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, T_SCC_BODY_TEXT_LINE=-0.01 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:315486 Archived-At: > I'm fine with it, on the condition that it continues to be possible to > print and read lambdas created by quoted function forms, as: > > #'(lambda () foo) The print format will be a sticking point, I expect. Currently on `master` it typically does not look like what you show above but like: (closure ENV (x y) (message "%S" x) (+ x y)) or (closure ENV (x y) DOCSTRING (interactive IFORM) (message "%S" x) (+ x = y)) For `prin1` with my PoC it currently looks like: #[(x y) ((message "%S" x) (+ x y)) ENV] or #[(x y) ((message "%S" x) (+ x y)) ENV nil DOCSTRING IFORM] and I'd rather not try to be too clever about it (it should be fairly rare to use `prin1` on such things). For `cl-print` we (and users) can choose, and I currently print it as #f(interpreted-function ARGS BODYHASH) because I basically kept the same code as used for compiled functions (obeying the same `cl-print-compiled` var) but we could make it look more "normal", like: #f(lambda (x y) (message "%S" x) (+ x y)) [ or #f(=CE=BB (x y) (message "%S" x) (+ x y)) =F0=9F=99=82 ] > Needless to say, funcall should continue to accept old list lambdas, > whether functionp regards them as such or not. No disagreement here. Stefan