From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28736@debbugs.gnu.org
Subject: bug#28736: 24.5; doc of `push'
Date: Sun, 8 Oct 2017 10:48:32 -0700 (PDT) [thread overview]
Message-ID: <9d23e7ad-ff25-4dac-b598-6614b272bebc@default> (raw)
In-Reply-To: <<83wp45sgrm.fsf@gnu.org>>
> > The right question is why is it a problem to document this?
>
> <Shrug> Because we don't want to guarantee the return value won't
> change in the future?
Are you sure? When was that decided? Just now?
Why would we want to do that? Gratuitously acting different
from Common Lisp (and all other Lisps?) in this case wouldn't
seem to be advantageous. Do you see a good reason to do that?
And why "<Shrug>"? I wonder if your answer might have been
different if a different person had filed this bug...
next parent reply other threads:[~2017-10-08 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<53afe0a4-8ce5-45fc-9e18-6bf52018c9b6@default>
[not found] ` <<<83h8vatbtk.fsf@gnu.org>
[not found] ` <<09655ed0-be2c-4453-9755-224ec733e221@default>
[not found] ` <<83wp45sgrm.fsf@gnu.org>
2017-10-08 17:48 ` Drew Adams [this message]
2017-10-08 18:13 ` bug#28736: 24.5; doc of `push' Eli Zaretskii
2021-09-25 15:41 ` Stefan Kangas
2021-09-25 16:43 ` bug#28736: [External] : " Drew Adams
[not found] <<<<53afe0a4-8ce5-45fc-9e18-6bf52018c9b6@default>
[not found] ` <<<<83h8vatbtk.fsf@gnu.org>
[not found] ` <<<09655ed0-be2c-4453-9755-224ec733e221@default>
[not found] ` <<<83wp45sgrm.fsf@gnu.org>
[not found] ` <<9d23e7ad-ff25-4dac-b598-6614b272bebc@default>
[not found] ` <<83tvz9se2s.fsf@gnu.org>
2017-10-08 19:40 ` Drew Adams
2017-10-09 7:13 ` Andreas Röhler
[not found] <<53afe0a4-8ce5-45fc-9e18-6bf52018c9b6@default>
[not found] ` <<83h8vatbtk.fsf@gnu.org>
2017-10-08 16:50 ` Drew Adams
2017-10-08 17:15 ` Eli Zaretskii
2017-10-08 2:56 Drew Adams
2017-10-08 6:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d23e7ad-ff25-4dac-b598-6614b272bebc@default \
--to=drew.adams@oracle.com \
--cc=28736@debbugs.gnu.org \
--cc=eliz@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.
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.