From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com, adam@alphapapa.net,
monnier@iro.umontreal.ca, arthur.miller@live.com
Subject: Re: Declaring Lisp function types
Date: Thu, 02 May 2024 13:22:15 +0300 [thread overview]
Message-ID: <86plu4ldig.fsf@gnu.org> (raw)
In-Reply-To: <yp1cyq55k43.fsf@fencepost.gnu.org> (message from Andrea Corallo on Wed, 01 May 2024 16:54:04 -0400)
> From: Andrea Corallo <acorallo@gnu.org>
> Cc: emacs-devel@gnu.org, stefankangas@gmail.com, adam@alphapapa.net,
> monnier@iro.umontreal.ca, arthur.miller@live.com
> Date: Wed, 01 May 2024 16:54:04 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Without any discussion of what can be @var{type} and no examples, this
> > is too abstract. I learned more about it from the other parts of the
> > changeset, where you actually use this. So please say something about
> > what can be @var{type}, and add one or two examples.
> >
> > Also, should we say something in NEWS about this?
>
> Entry added.
>
> Please let me know if you like me to merge it or I can improve it
> further.
Thanks. I still have a few minor comments below, but we can handle
these after this lands on master.
> +@var{type} is a type specifier in the form @code{(function (ARG-1-TYPE
> +... ARG-N-TYPE) RETURN-TYPE)}. Argument types can be interleaved with
The @code{..} part should be wrapped in @w{..}, to prevent its
breaking between two lines.
> +symbols @code{&optional} and @code{&rest} to match the @pxref{Argument
> +List} of the function.
This is not a good use of @pxref. You want @ref there. Moreover,
such HTML-like style of cross-references doesn't work well in Texinfo,
because at least the info and the printed output formats add stuff,
like "See" to the reference. So my recommendation is to use a wordier
...to match the function's arguments (@pxref{Argument List}).
> +@lisp
> +(defun positive-p (x)
> + (declare (type (function (number) boolean)))
> + (when (> x 0)
> + t))
> +@end lisp
If you don't want to have the example broken between two pages, use
@group:
@lisp
@group
(defun positive-p (x)
(declare (type (function (number) boolean)))
(when (> x 0)
t))
@end group
@end lisp
> +@lisp
> +(defun cons-or-number (x &optional err-msg)
> + (declare (type (function ((or cons number) &optional string)
> + (member is-cons is-number))))
> + (if (consp x)
> + 'is-cons
> + (if (numberp x)
> + 'is-number
> + (error (or err-msg "Unexpected input")))))
> +@end lisp
Same here.
> +More types are described in @pxref{Lisp Data Types}.
The problematic cross-reference again.
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -1935,6 +1935,10 @@ unibyte string.
> \f
> * Lisp Changes in Emacs 30.1
>
> +** Function type declaration
This should end in a period. Also, since you have updated the manual,
it should be marked with "+++".
> +It is now possible, using the 'declare' macro, to declare expected types
> +of function arguments and return type.
Suggest to reword:
It is now possible to declare the expected type of a function's
arguments using the 'declare' macro.
next prev parent reply other threads:[~2024-05-02 10:22 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86plu4ldig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acorallo@gnu.org \
--cc=adam@alphapapa.net \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).