From: Marco Antoniotti <marco.antoniotti@unimib.it>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: (declare (type (function...
Date: Fri, 10 May 2024 11:50:03 +0200 [thread overview]
Message-ID: <CAG0Nw2mA6mM_tFX+HH-CecKzEtWR53gUHi2GFVKcJD=-yELcJg@mail.gmail.com> (raw)
In-Reply-To: <yp1wmo2w4co.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Dear Andrea
The point is NOT to diverge from Common Lisp. Such divergence is - IMHO -
unwarranted. Plus, the proposal for the ftype declaration also carries
over to type declarations, which, again, are useful per se, even if the
compiler is "smart enough" (ok; this one is for old-timers :) )
Having said that, a provision can be made that a nameless ftype declaration
at a function top level refers to the "definenda" function. Again, having
to use ftype instead of type is a consequence of ELisp being a 2-lisp.
Cheers
MA
On Fri, May 10, 2024 at 8:47 AM Andrea Corallo <acorallo@gnu.org> wrote:
> Marco Antoniotti <marco.antoniotti@unimib.it> writes:
>
> > Ciao Andrea
> >
> > The presentation I attended gave me the idea of "ranting talks" at the
> next ELS :)
> >
> > Having said so, I now think that, to save goat and cabbage, what you
> want is
> >
> > (defun foo (x y)
> > (declare (ftype (function (integer number) number) foo))
> > (+ x y))
> >
> > Common lispers can live with that.
> >
> > All the best
> >
> > MA
>
> Ciao Mario,
>
> not sure what maintainers think about it, I'm not in love with this
> solution because one has to repeat 'foo' two times and we don't support
> anyway unsing declare inside a function to declare another one.
>
> Mmmhh
>
> Andrea
>
--
Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01
DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it
Viale Sarca 336
I-20126 Milan (MI) ITALY
[-- Attachment #2: Type: text/html, Size: 2592 bytes --]
next prev parent reply other threads:[~2024-05-10 9:50 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 [this message]
2024-05-10 10:21 ` Andrea Corallo
2024-05-10 11:53 ` Marco Antoniotti
2024-05-10 14:04 ` Stefan Monnier
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='CAG0Nw2mA6mM_tFX+HH-CecKzEtWR53gUHi2GFVKcJD=-yELcJg@mail.gmail.com' \
--to=marco.antoniotti@unimib.it \
--cc=acorallo@gnu.org \
--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.