From: Andrea Corallo <acorallo@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Declaring Lisp function types
Date: Mon, 26 Feb 2024 11:25:40 -0500 [thread overview]
Message-ID: <yp1cysj6vln.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <ZdtzHjbxCtX5m3jj@ACM> (Alan Mackenzie's message of "Sun, 25 Feb 2024 17:04:30 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Hello, Andrea.
>
> On Fri, Feb 23, 2024 at 11:02:52 -0500, Andrea Corallo wrote:
>> Hi all,
>
>> I'm looking into moving out the function type declarations in
>> 'comp-known-type-specifiers' in order to move them to where the function
>> are actually defined. This to easy maintenance (ATM they get out of
>> sync) and to allow the user for (indeed optionally) declaring function
>> types.
>
>> In principle I believe we are interested in expressing the the argument
>> types and (maybe optionally) the return type.
>
> What's missing is the why. Do we actually want to put function type
> declarations in Lisp source at all? They will clutter up the code more
> than it is cluttered up at the moment.
Hi Alan,
just to confirm that I think the explainations you've got form Eli and
Drew are I think a good summary.
Thanks
Andrea
next prev parent reply other threads:[~2024-02-26 16:25 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:02 Declaring Lisp function types Andrea Corallo
2024-02-23 23:35 ` Adam Porter
2024-02-24 7:10 ` Eli Zaretskii
2024-02-24 8:53 ` Tomas Hlavaty
2024-02-24 9:08 ` Adam Porter
2024-02-24 9:24 ` Andrea Corallo
2024-02-24 15:13 ` Tomas Hlavaty
2024-02-24 15:21 ` Tomas Hlavaty
2024-02-24 15:24 ` Tomas Hlavaty
2024-02-24 8:56 ` Adam Porter
2024-02-24 10:03 ` Eli Zaretskii
2024-02-25 7:35 ` Adam Porter
2024-02-24 9:21 ` Andrea Corallo
2024-02-25 17:04 ` Alan Mackenzie
2024-02-25 17:15 ` Eli Zaretskii
2024-02-25 17:16 ` [External] : " Drew Adams
2024-02-26 16:25 ` Andrea Corallo [this message]
2024-02-29 3:50 ` Richard Stallman
2024-02-29 6:10 ` Adam Porter
2024-02-29 9:02 ` Andrea Corallo
2024-02-26 3:38 ` Richard Stallman
2024-02-26 16:38 ` [External] : " Drew Adams
2024-02-26 16:54 ` Eli Zaretskii
2024-02-26 17:44 ` Andrea Corallo
2024-02-26 16:52 ` Andrea Corallo
2024-02-26 18:10 ` Tomas Hlavaty
2024-03-02 21:19 ` Stefan Monnier via Emacs development discussions.
2024-03-03 9:52 ` Andrea Corallo
2024-03-03 14:52 ` Stefan Monnier
2024-03-03 17:31 ` Andrea Corallo
2024-03-03 18:13 ` Stefan Monnier
2024-03-15 16:49 ` Andrea Corallo
2024-03-15 18:19 ` Tomas Hlavaty
2024-03-15 18:38 ` Eli Zaretskii
2024-03-16 13:39 ` Tomas Hlavaty
2024-03-16 14:06 ` Eli Zaretskii
2024-03-16 14:56 ` Tomas Hlavaty
2024-03-16 15:43 ` Emanuel Berg
2024-03-16 15:44 ` Eli Zaretskii
2024-03-16 15:54 ` Emanuel Berg
2024-03-18 8:55 ` Lele Gaifax
2024-03-16 0:01 ` Adam Porter
2024-03-18 9:25 ` Andrea Corallo
2024-03-26 10:13 ` Andrea Corallo
2024-03-26 10:28 ` Christopher Dimech
2024-03-26 12:55 ` Eli Zaretskii
2024-03-26 16:46 ` Andrea Corallo
2024-04-29 17:48 ` Andrea Corallo
2024-04-29 17:55 ` Stefan Monnier
2024-04-29 18:42 ` Andrea Corallo
2024-04-30 14:55 ` Eli Zaretskii
2024-04-30 18:29 ` Stefan Monnier
2024-05-01 20:57 ` Andrea Corallo
2024-05-01 21:06 ` Stefan Monnier
2024-05-02 6:16 ` Eli Zaretskii
2024-05-02 10:16 ` Andrea Corallo
2024-05-02 6:15 ` Eli Zaretskii
2024-05-02 10:12 ` Andrea Corallo
2024-05-02 11:15 ` Eli Zaretskii
2024-05-02 13:20 ` Stefan Monnier
2024-05-01 20:54 ` Andrea Corallo
2024-05-02 10:22 ` Eli Zaretskii
2024-05-02 15:18 ` Andrea Corallo
2024-05-02 16:32 ` Eli Zaretskii
2024-03-26 13:05 ` Mattias Engdegård
2024-03-26 13:44 ` Stefan Monnier
2024-03-26 14:28 ` Joost Kremers
2024-03-26 14:37 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2024-03-16 7:46 Arthur Miller
2024-03-16 15:46 ` Emanuel Berg
2024-03-18 9:02 ` Andrea Corallo
2024-03-18 9:58 ` Arthur Miller
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=yp1cysj6vln.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
/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.