unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>,
	Adam Porter <adam@alphapapa.net>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Arthur Miller <arthur.miller@live.com>
Subject: Re: Declaring Lisp function types
Date: Tue, 26 Mar 2024 11:28:06 +0100	[thread overview]
Message-ID: <trinity-665f5bee-36a4-4aa1-b5a2-93e66d3fea37-1711448886234@3c-app-mailcom-bs15> (raw)
In-Reply-To: <yp17chpqp15.fsf@fencepost.gnu.org>

> Sent: Tuesday, March 26, 2024 at 10:13 PM
> From: "Andrea Corallo" <acorallo@gnu.org>
> To: emacs-devel@gnu.org
> Cc: "Eli Zaretskii" <eliz@gnu.org>, "Stefan Kangas" <stefankangas@gmail.com>, "Adam Porter" <adam@alphapapa.net>, "Stefan Monnier" <monnier@iro.umontreal.ca>, "Arthur Miller" <arthur.miller@live.com>
> Subject: Re: Declaring Lisp function types
>
> Andrea Corallo <acorallo@gnu.org> writes:
>
> > I'd like to progress on this but in order to do that we should pick a
> > syntax.
> >
> > Of the three most discussed syntaxes in this thread my order of
> > preference is (by examples):
> >
> > 1:
> >
> > (defun sum (a b)
> >   (declare (function (integer integer) integer))
> >   (+ a b))
> >
> > 2:
> >
> > (defun sum (a b)
> >   (declare (type (function (integer integer) integer)))
> >   (+ a b))
> >
> > 3:
> >
> > (defun sum (a b)
> >   (declare (type (integer integer) integer))
> >   (+ a b))
> >
> > For the reasons I've already expressed: 1 I like it, 2 I'm okay with it,
> > 3 I very much dislike it.
> >
> > Maintainers WDYT?
> >
> > Thanks
> >
> >   Andrea
>
> To make a summary of my understanding of this conversation on the
> various options so far:
>
> A couple of people mentioned would be a good idea to consider CL's
> syntax but this is problematic for how our declare machinery works.
>
> I think Eli and I preferred solution 1.

I approve of preferred solution 1

> Stefan suggested we go for 2 as it's more verbose (and this should
> discourage users at using it too much).

Do not like increase of verbosity or intentions towards discouraging
functionalities that are inherently acceptable to use.  If some things
should not be done, there should be no tools for them, especially not
emanating from an official release, as I am more for robustness as the
ultimate completion step.

> Adam strongly opposed to 1 as it conflicts with his proposal [1] but
> AFAIU he agreed later on that thread on another solution so I guess the
> conflict should not be there anymore.
>
> If I've miss-summarized any opinion indeed please feel free to rectify.
>
> I think we should make a decision (maintainers) so we can progress on
> this.
>
> Thanks
>
>   Andrea
>
> [1] <https://lists.gnu.org/archive/html/emacs-devel/2024-03/msg00118.html>
>
>



  reply	other threads:[~2024-03-26 10:28 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 [this message]
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

  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=trinity-665f5bee-36a4-4aa1-b5a2-93e66d3fea37-1711448886234@3c-app-mailcom-bs15 \
    --to=dimech@gmx.com \
    --cc=acorallo@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=arthur.miller@live.com \
    --cc=eliz@gnu.org \
    --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).