From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Marco Antoniotti <marco.antoniotti@unimib.it>,
emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: (declare (type (function...
Date: Fri, 10 May 2024 10:04:38 -0400 [thread overview]
Message-ID: <jwv7cg1kbn0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yp14jb6vufy.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Fri, 10 May 2024 06:21:21 -0400")
>> The point is NOT to diverge from Common Lisp. Such divergence is -
>> IMHO - unwarranted.
CL is a good inspiration in general, but ELisp is not and never will be
Common-Lisp, so it's not indispensable to adhere to its choices.
I think its provision of type annotation is not great, so there isn't
a strong need to follow it.
> I see your point and share the intent, given your provision 😃 for
>
> (defun foo (x y)
> (declare (ftype (function (integer number) number)))
> (+ x y))
>
> I'm personally okay with the change.
No objection here either.
Stefan
next prev parent reply other threads:[~2024-05-10 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 11:55 (declare (type (function Marco Antoniotti
2024-05-07 16:55 ` Tomas Hlavaty
2024-05-07 17:10 ` Marco Antoniotti
2024-05-07 17:38 ` Tomas Hlavaty
2024-05-07 17:52 ` Marco Antoniotti
2024-05-07 20:32 ` Andrea Corallo
2024-05-08 2:36 ` Emanuel Berg
2024-05-09 3:21 ` Tomas Hlavaty
2024-05-08 2:44 ` Emanuel Berg
2024-05-08 11:36 ` Marco Antoniotti
2024-05-09 3:33 ` Tomas Hlavaty
2024-05-09 13:19 ` Simon Leinen
2024-05-09 13:43 ` Emanuel Berg
2024-05-10 6:47 ` Andrea Corallo
2024-05-10 9:50 ` Marco Antoniotti
2024-05-10 10:21 ` Andrea Corallo
2024-05-10 11:53 ` Marco Antoniotti
2024-05-10 14:04 ` Stefan Monnier [this message]
2024-05-10 14:17 ` Marco Antoniotti
2024-05-11 10:29 ` Eli Zaretskii
2024-05-13 21:12 ` Andrea Corallo
2024-05-14 9:26 ` Andrea Corallo
2024-05-14 10:04 ` Marco Antoniotti
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=jwv7cg1kbn0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=marco.antoniotti@unimib.it \
/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.