From: Tomas Hlavaty <tom@logand.com>
To: Alan Mackenzie <acm@muc.de>, Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, mattias.engdegard@gmail.com,
stefankangas@gmail.com
Subject: Re: Introducing 'safety' compilation parameter
Date: Tue, 07 May 2024 18:37:52 +0200 [thread overview]
Message-ID: <87jzk58tnj.fsf@neko.mail-host-address-is-not-set> (raw)
In-Reply-To: <ZjoYHQ5cHPqpKInW@ACM>
On Tue 07 May 2024 at 12:01, Alan Mackenzie <acm@muc.de> 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 <eliz@gnu.org> (March 16)
Subject: Re: Declaring Lisp function types
To: Tomas Hlavaty <tom@logand.com>
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.
[...]
next prev parent reply other threads:[~2024-05-07 16:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 10:37 Introducing 'safety' compilation parameter Andrea Corallo
2024-05-07 12:01 ` Alan Mackenzie
2024-05-07 13:15 ` Eli Zaretskii
2024-05-07 16:07 ` Drifting towards a statically typed Emacs Lisp. [Was: Introducing 'safety' compilation parameter] Alan Mackenzie
2024-05-07 17:06 ` Andrea Corallo
2024-05-07 23:37 ` Emanuel Berg
2024-05-07 18:00 ` Eli Zaretskii
2024-05-08 0:14 ` Emanuel Berg
2024-05-07 23:29 ` Emanuel Berg
2024-05-09 23:52 ` Richard Stallman
2024-05-10 6:31 ` Eli Zaretskii
2024-05-07 16:37 ` Tomas Hlavaty [this message]
2024-05-07 16:54 ` Introducing 'safety' compilation parameter Andrea Corallo
2024-05-07 23:42 ` Emanuel Berg
2024-05-07 14:56 ` Stefan Monnier
2024-05-07 16:13 ` Andrea Corallo
2024-05-10 17:58 ` Andrea Corallo
2024-05-13 2:29 ` Stefan Monnier
2024-05-13 18:59 ` Eli Zaretskii
2024-05-13 21:12 ` Andrea Corallo
2024-05-14 6:11 ` Eli Zaretskii
2024-05-09 8:40 ` Eli Zaretskii
2024-05-10 7:47 ` Andrea Corallo
2024-05-10 10:17 ` Eli Zaretskii
2024-05-10 11:42 ` Andrea Corallo
2024-05-10 15:10 ` Eli Zaretskii
2024-05-10 18:02 ` Andrea Corallo
2024-05-10 18:05 ` Andrea Corallo
2024-05-09 9:19 ` Gerd Möllmann
2024-05-10 7:58 ` Andrea Corallo
2024-05-10 8:09 ` Gerd Möllmann
2024-05-10 8:19 ` Andrea Corallo
2024-05-10 14:00 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzk58tnj.fsf@neko.mail-host-address-is-not-set \
--to=tom@logand.com \
--cc=acm@muc.de \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.