From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Nagy <danielnagy@posteo.de>
Cc: 66890@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument
Date: Sun, 05 Nov 2023 07:35:30 +0200 [thread overview]
Message-ID: <83edh44va5.fsf@gnu.org> (raw)
In-Reply-To: <87jzqxgrof.fsf@posteo.de> (message from Daniel Nagy on Sat, 04 Nov 2023 20:57:41 +0000)
> Cc: 66890@debbugs.gnu.org
> From: Daniel Nagy <danielnagy@posteo.de>
> Date: Sat, 04 Nov 2023 20:57:41 +0000
>
> In general, I would say that, if the computer can unambigously decide
> what is supposed to happen, it should help me and automatically correct
> my "mistakes".
IME, this is a somewhat dangerous tendency. In practice, it is easy
for a program to mistakenly interpret invalid inputs as some
transformation of valid ones, and do something that is very far from
what the caller meant. So whether to "correct mistakes" or fail the
call is largely a judgment call, and it is not an accident that most
APIs prefer to fail in those cases, reserving the "correction" path
only for documented polymorphic situations.
next prev parent reply other threads:[~2023-11-05 5:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:31 bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument Daniel Nagy
2023-11-02 6:32 ` Eli Zaretskii
2023-11-02 19:38 ` Stefan Kangas
2023-11-02 20:55 ` Daniel Nagy
2023-11-03 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 0:21 ` Stefan Kangas
2023-11-04 6:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 10:43 ` Stefan Kangas
2023-11-04 20:57 ` Daniel Nagy
2023-11-04 22:12 ` Drew Adams
2023-11-05 5:35 ` Eli Zaretskii [this message]
2023-11-05 23:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87bkcbzy6c.fsf@posteo.de>
2023-11-03 6:46 ` Eli Zaretskii
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=83edh44va5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66890@debbugs.gnu.org \
--cc=danielnagy@posteo.de \
--cc=monnier@iro.umontreal.ca \
/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).