From: Tomas Hlavaty <tom@logand.com>
To: Emanuel Berg <incal@dataswamp.org>, emacs-devel@gnu.org
Subject: Re: (declare (type (function...
Date: Thu, 09 May 2024 05:21:03 +0200 [thread overview]
Message-ID: <877cg3hdr4.fsf@neko.mail-host-address-is-not-set> (raw)
In-Reply-To: <8734qt81xx.fsf@dataswamp.org>
On Wed 08 May 2024 at 04:36, Emanuel Berg <incal@dataswamp.org> wrote:
> 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.
function-signature is already an established concept in emacs:
find -H . -type d \( -path \*/SCCS -o -path \*/RCS -o -path \*/CVS -o -path \*/MCVS -o -path \*/.src -o -path \*/.svn -o -path \*/.git -o -path \*/.hg -o -path \*/.bzr -o -path \*/_MTN -o -path \*/_darcs -o -path \*/\{arch\} \) -prune -o \! -type d \( -name .\#\* -o -name \*.o -o -name \*\~ -o -name \*.bin -o -name \*.lbin -o -name \*.so -o -name \*.a -o -name \*.ln -o -name \*.blg -o -name \*.bbl -o -name \*.elc -o -name \*.lof -o -name \*.glo -o -name \*.idx -o -name \*.lot -o -name \*.fmt -o -name \*.tfm -o -name \*.class -o -name \*.fas -o -name \*.lib -o -name \*.mem -o -name \*.x86f -o -name \*.sparcf -o -name \*.dfsl -o -name \*.pfsl -o -name \*.d64fsl -o -name \*.p64fsl -o -name \*.lx64fsl -o -name \*.lx32fsl -o -name \*.dx64fsl -o -name \*.dx32fsl -o -name \*.fx64fsl -o -name \*.fx32fsl -o -name \*.sx64fsl -o -name \*.sx32fsl -o -name \*.wx64fsl -o -name \*.wx32fsl -o -name \*.fasl -o -name \*.ufsl -o -name \*.fsl -o -name \*.dxl -o -name \*.lo -o -name \*.la -o -name \*.gmo -o -name \*.mo -o -name \*.toc -o -name \*.aux -o -name \*.cp -o -name \*.fn -o -name \*.ky -o -name \*.pg -o -name \*.tp -o -name \*.vr -o -name \*.cps -o -name \*.fns -o -name \*.kys -o -name \*.pgs -o -name \*.tps -o -name \*.vrs -o -name \*.pyc -o -name \*.pyo \) -prune -o -type f \( -name \*.\* \) -exec grep --color=auto -i -nH --null -e function-signature \{\} +
./lisp/emacs-lisp/bytecomp.el1486:(defun byte-compile--function-signature (f)
./lisp/emacs-lisp/bytecomp.el1571: (sig (cond (def (byte-compile--function-signature def))
./lisp/emacs-lisp/bytecomp.el1708: (let ((sig1 (byte-compile--function-signature old))
./lisp/progmodes/octave.el1593:(defun octave-eldoc-function-signatures (fn)
./lisp/progmodes/octave.el1641: (sigs (and fn (octave-eldoc-function-signatures fn)))
./lisp/ChangeLog.1722998: (octave-eldoc-function-signatures, octave-help)
./lisp/ChangeLog.1724611: (octave-eldoc-function-signatures, octave-eldoc-function):
./test/lisp/emacs-lisp/bytecomp-tests.el1156: "warn-wide-docstring-ignore-function-signature.el"
./ChangeLog.350951: * lisp/progmodes/octave.el (octave-eldoc-function-signatures): Use
./ChangeLog.3170940: * lisp/progmodes/octave.el (octave-eldoc-function-signatures): Fix the
./ChangeLog.3171565: byte-compile--function-signature, it fails to compile code which
./ChangeLog.3194592: * lisp/emacs-lisp/bytecomp.el (byte-compile--function-signature): New fun.
./ChangeLog.3194596: since bytecode functions are now handled in byte-compile--function-signature.
next prev parent reply other threads:[~2024-05-09 3:21 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cg3hdr4.fsf@neko.mail-host-address-is-not-set \
--to=tom@logand.com \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.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.