unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: (declare (type (function...
Date: Wed, 08 May 2024 04:36:26 +0200	[thread overview]
Message-ID: <8734qt81xx.fsf@dataswamp.org> (raw)
In-Reply-To: yp1a5l1xt11.fsf@fencepost.gnu.org

Andrea Corallo wrote:

> I've no problem changing 'type' for something different if
> there's agreement, I don't especially like 'signature' as
> it's a bit verbose for my taste (but I could leave with it).

I think "signature" is extremely old school, by now completely
unintuitive terminology to everyone but a precious few.

But gpt4 sticks with it, so maybe?

Q: What is the difference between function declaration,
   prototype, and signature?
            
A: Function declaration defines the function, prototype
   declares its existence, and signature specifies its inputs
   and outputs.

As for greping source, searching code in buffers for unique
strings etc - and just in general - when something new and
fancy is introduced, it is always a good idea to give it a new
and fancy and, optimally, unique name. But if there isn't such
a name that makes sense in terms of technology it is also
never wrong to just call it whatever it is.

Maybe one can combine two words, declare type, type signature
... You can use apropos to see if you get any hits. It'll be
more cryptic but also unique and more cool in a way B)
`tsig' :)

BTW, in Python, there is a function signature concept that
isn't equal to this type signature concept.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2024-05-08  2:36 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 [this message]
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
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

  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=8734qt81xx.fsf@dataswamp.org \
    --to=incal@dataswamp.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 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).