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: Short functions Date: Mon, 06 Jan 2025 12:25:27 -0500 Message-ID: References: <173617561349.1583674.17727386803499537943@vcs3.savannah.gnu.org> <20250106150015.2A1DD1043A07@vcs3.savannah.gnu.org> <87cygz7wl8.fsf@daniel-mendler.de> <6B4F0218-6692-4CD2-BECD-0C7CA047FC3E@dancol.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="15278"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org, Daniel Mendler To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 06 18:26:43 2025 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 1tUqsF-0003oo-M5 for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Jan 2025 18:26:43 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tUqrL-0006Qt-D0; Mon, 06 Jan 2025 12:25:47 -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 1tUqrI-0006QT-QG for emacs-devel@gnu.org; Mon, 06 Jan 2025 12:25:44 -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 1tUqr9-0003oK-Sn for emacs-devel@gnu.org; Mon, 06 Jan 2025 12:25:40 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 2BBB5100043; Mon, 6 Jan 2025 12:25:30 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1736184328; bh=JELrmuYU6CHJ7KCeiS5/fZs8/mxBpfivZhrP/TSE53I=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Y2otYfBdnAxKsIF592aeg5Uk1kUXn+U/AJzF++kHb6ybl4SBRueUPoOCF5pV0B/6X hAWMW5Qir+IwMzqyyfoNEu2LZ1IktUWg7lfqtD1CjTyfgKxndUA3To0IaGVx+A2/IJ 5P2qr3oK0zwsfs2VkYorkMoht5Xyyhxvh5SFnRvpBV7dojpojKpxAnrdYncXgbbd2U 2iSOGVPZpSc6JwSIqRkSGqjOsOU2wVzaXsQDqqK64S+L99qAAs70GYs5Vx8NG1Lxx/ lFWwhLE/7UTRymSLm5Ts+hqr6J6BQRTm+59Jii3kS6kXMn6LsejlqnI2Uar25QbEN7 gJJuRCs24UJLA== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id A7413100035; Mon, 6 Jan 2025 12:25:28 -0500 (EST) Original-Received: from alfajor (modemcable005.21-80-70.mc.videotron.ca [70.80.21.5]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7D8E5120346; Mon, 6 Jan 2025 12:25:28 -0500 (EST) In-Reply-To: <6B4F0218-6692-4CD2-BECD-0C7CA047FC3E@dancol.org> (Daniel Colascione's message of "Mon, 06 Jan 2025 11:57:46 -0500") 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327745 Archived-At: >> more efficient, we'd want to avoid both heap allocation and recursion, >> but sadly from ELisp the only way to allocate non-heap memory is via >> recursion. > Hopefully, generational GC will make heap allocation much less burdensome > and the need for stack allocation (and escape analysis) less pressing. +1 (and concurrent GC would also do the trick since we can generally assume that there are free cycles available on another core) Still, I keep hoping for a clever way to allow explicit avoidance of heap allocation for those cases where the coder can be bothered to make extra efforts for that. Stefan