From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Drifting towards a statically typed Emacs Lisp. [Was: Introducing 'safety' compilation parameter] Date: Wed, 08 May 2024 01:37:04 +0200 Message-ID: <87ikzp8a8v.fsf@dataswamp.org> References: <86v83pahks.fsf@gnu.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="36520"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:tTlI9SNA6l7Rz93GeyaPl3cQXWc= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 08 04:22:56 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 1s4WxM-0009KQ-TJ for ged-emacs-devel@m.gmane-mx.org; Wed, 08 May 2024 04:22:56 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s4Wwy-0004bL-2s; Tue, 07 May 2024 22:22:32 -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 1s4UMz-0002Sl-Pt for emacs-devel@gnu.org; Tue, 07 May 2024 19:37:13 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s4UMy-0004UD-2s for emacs-devel@gnu.org; Tue, 07 May 2024 19:37:13 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1s4UMv-0008Bw-Kz for emacs-devel@gnu.org; Wed, 08 May 2024 01:37:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 07 May 2024 22:22:30 -0400 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:318981 Archived-At: Andrea Corallo wrote: > Because it can be informative (when there are types other > than t), anyway you can control it with > 'help-display-function-type' if you don't want to have it in > the *Help* buffer. Ah, so you already added what I asked for/suggested in my other post. Okay good, all the better then. >> If this is the way Emacs Lisp is to develop, can't we at >> least have an open discussion about it and a positive >> decision taken, rather than letting it "just happen"? As is >> already clear, I see static typing in Emacs Lisp, except, >> perhaps, on a very limited scale, as a Bad Thing. > > Again, there's no plan to make elisp statically typed. > I agree with you this is a tool to be used on a limited > scale, if this is not clear enough from the doc now I guess > we can just improve it. I think it is cool with the inferred type system, as well as the possibility to have explicit types for functions, arguments, etc, in source. Those types could be used in many different ways at compile as well as run time, that doesn't mean we must "make Elisp statically typed". -- underground experts united https://dataswamp.org/~incal