From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: Is it ok to sort a list of overlays destructively?
Date: Thu, 29 Jul 2021 08:11:46 -0700 [thread overview]
Message-ID: <YQLFMhabWpUq1CXS@scrozzle> (raw)
In-Reply-To: <83mtq5s3jg.fsf@gnu.org>
On 2021-07-29 at 15:33:23 +0300,
Eli Zaretskii <eliz@gnu.org> wrote:
> > From: John Yates <john@yates-sheets.org>
> > Date: Thu, 29 Jul 2021 07:34:07 -0400
> > Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
> >
> > On Wed, Jul 28, 2021 at 7:44 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > > Basically, you should assume that Emacs protects itself where that is
> > > needed, so if it handed you a list or some other data, and nothing in
> > > the doc string warns you against doing something with that data, you
> > > are free to do that, and if that causes unexpected results, there's
> > > either a documentation bug or a code bug that needs to be fixed.
> >
> > I am not sure if such a statement exists in any of the manuals. Should
> > it not be stated explicitly somewhere?
>
> I don't think it should be, no. It's pretty much obvious, IMO.
I'm not disagreeing, but why is it obvious? Not all software works that
way (it would be great if it did), whether the authors thought about it
at all and/or intended it to work one way or the other, or not.
next prev parent reply other threads:[~2021-07-29 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 5:22 Is it ok to sort a list of overlays destructively? Marcin Borkowski
2021-07-27 9:40 ` tomas
2021-07-27 10:07 ` Marcin Borkowski
2021-07-27 13:49 ` Eli Zaretskii
2021-07-27 20:14 ` Marcin Borkowski
2021-07-28 2:25 ` Eli Zaretskii
2021-07-28 6:06 ` Marcin Borkowski
2021-07-28 11:44 ` Eli Zaretskii
2021-07-29 11:34 ` John Yates
2021-07-29 12:33 ` Eli Zaretskii
2021-07-29 15:11 ` 2QdxY4RzWzUUiLuE [this message]
2021-07-29 15:30 ` Eli Zaretskii
2021-07-29 16:20 ` 2QdxY4RzWzUUiLuE
2021-07-29 16:53 ` Eli Zaretskii
2021-07-30 19:27 ` Marcin Borkowski
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=YQLFMhabWpUq1CXS@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--cc=help-gnu-emacs@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.
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).