From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tomas Hlavaty Newsgroups: gmane.emacs.devel Subject: Re: Introducing 'safety' compilation parameter Date: Tue, 07 May 2024 18:37:52 +0200 Message-ID: <87jzk58tnj.fsf@neko.mail-host-address-is-not-set> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26578"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, Eli Zaretskii , monnier@iro.umontreal.ca, mattias.engdegard@gmail.com, stefankangas@gmail.com To: Alan Mackenzie , Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 07 18:39:18 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 1s4NqY-0006ZR-3A for ged-emacs-devel@m.gmane-mx.org; Tue, 07 May 2024 18:39:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s4NpQ-0005BQ-4w; Tue, 07 May 2024 12:38:08 -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 1s4NpP-0005B8-0U for emacs-devel@gnu.org; Tue, 07 May 2024 12:38:07 -0400 Original-Received: from logand.com ([37.48.87.44]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s4NpN-0000oT-Ke; Tue, 07 May 2024 12:38:06 -0400 Original-Received: by logand.com (Postfix, from userid 1001) id B02AE19E895; Tue, 7 May 2024 18:37:54 +0200 (CEST) X-Mailer: emacs 28.2 (via feedmail 11-beta-1 I) In-Reply-To: Received-SPF: pass client-ip=37.48.87.44; envelope-from=tom@logand.com; helo=logand.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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:318959 Archived-At: On Tue 07 May 2024 at 12:01, Alan Mackenzie wrote: > turning > Emacs Lisp into a statically typed language. If this change gets merged > into master, how long will it be until these function declarations > become first common, then usual, then all but universal? It that were > to happen, it would be, in my opinion, a net loss to Emacs. this looks like the plan: id:86sf0q5l0v.fsf@gnu.org Eli Zaretskii (March 16) Subject: Re: Declaring Lisp function types To: Tomas Hlavaty Cc: acorallo@gnu.org, emacs-devel@gnu.org, stefankangas@gmail.com Date: Sat, 16 Mar 2024 16:06:08 +0200 [...] By contrast, _every_ function will have some type and some signature, so you will have a gazillion of hits if you search for those, no matter what its name. [...]