From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: rpluim@gmail.com, 65030@debbugs.gnu.org, eller.helmut@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#65030: 30.0.50; Check keyword args of make-process
Date: Tue, 08 Aug 2023 15:16:51 +0300 [thread overview]
Message-ID: <83350tohjg.fsf@gnu.org> (raw)
In-Reply-To: <0E5BAD91-FE2A-4622-9F76-26E8CEB8F71A@acm.org> (message from Mattias Engdegård on Tue, 8 Aug 2023 11:16:07 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 8 Aug 2023 11:16:07 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>,
> eller.helmut@gmail.com, 65030@debbugs.gnu.org
>
> > Mattias> The main objection is that `make-process`, due to its design, is often
> > Mattias> called indirectly using `apply` which would not trigger the
> > Mattias> application of this compiler macro, so perhaps we should improve the
> > Mattias> error handling of Fmake_process instead.
> >
> > As long as that improvement results in warnings for mistakes such as
> > misspelled keywords, rather than errors.
>
> Of course not. Incorrect arguments detected at run-time should elicit errors, as they do now.
> The point being that for something as complex as make-process they should be more helpful than just `wrong-type-argument`.
Misspelled arguments to make-process don't elicit errors as of now, do
they?
next prev parent reply other threads:[~2023-08-08 12:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 6:47 bug#65030: 30.0.50; Check keyword args of make-process Helmut Eller
2023-08-05 9:21 ` Eli Zaretskii
2023-08-05 23:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-06 4:58 ` Eli Zaretskii
2023-08-06 8:49 ` Mattias Engdegård
2023-08-08 8:52 ` Robert Pluim
2023-08-08 9:16 ` Mattias Engdegård
2023-08-08 9:27 ` Robert Pluim
2023-08-08 9:42 ` Mattias Engdegård
2023-08-08 12:16 ` Eli Zaretskii [this message]
2023-08-08 13:05 ` Mattias Engdegård
2023-08-08 13:18 ` Robert Pluim
2023-08-08 16:38 ` Mattias Engdegård
2023-08-08 17:14 ` Helmut Eller
2023-08-08 20:15 ` Mattias Engdegård
2023-08-08 17:43 ` Eli Zaretskii
2023-08-08 17:51 ` Mattias Engdegård
2023-08-08 17:54 ` Stefan Kangas
2023-08-08 18:28 ` Eli Zaretskii
2023-08-08 13:37 ` Visuwesh
2023-08-08 13:52 ` Robert Pluim
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=83350tohjg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65030@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).