unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	65030@debbugs.gnu.org, eller.helmut@gmail.com,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65030: 30.0.50; Check keyword args of make-process
Date: Tue, 8 Aug 2023 11:16:07 +0200	[thread overview]
Message-ID: <0E5BAD91-FE2A-4622-9F76-26E8CEB8F71A@acm.org> (raw)
In-Reply-To: <87sf8tapbf.fsf@gmail.com>

8 aug. 2023 kl. 10.52 skrev Robert Pluim <rpluim@gmail.com>:

> I donʼt think any of the `make-process' keywords accept keywords as
> values, but missing values tends to cause catastrophic failure, so I
> donʼt think itʼs that common a mistake.

No, the usefulness of good compiler warnings goes far beyond that. A determined programmer may eventually get something working despite an error-prone API, but decent diagnostics will speed up the process manifold by pointing out mistakes before the code is even run. (With flymake/flycheck, even faster.)

>    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`.






  reply	other threads:[~2023-08-08  9: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 [this message]
2023-08-08  9:27             ` Robert Pluim
2023-08-08  9:42               ` Mattias Engdegård
2023-08-08 12:16             ` Eli Zaretskii
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=0E5BAD91-FE2A-4622-9F76-26E8CEB8F71A@acm.org \
    --to=mattiase@acm.org \
    --cc=65030@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --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).