From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Robin Templeton <robin@terpri.org>, 19790@debbugs.gnu.org
Subject: bug#19790: [PATCH] destructive splicing in backquote
Date: Sun, 08 Feb 2015 22:10:01 -0500 [thread overview]
Message-ID: <jwvtwyvyecx.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAAdUY-+9bAouE2TEnXxysmXh=51gKqdaE6if3vWYGHN80SjUTA@mail.gmail.com> (Artur Malabarba's message of "Sun, 8 Feb 2015 17:38:56 -0200")
> I'm fine with using this syntax for destructive splicing or with
> disabling it altogether. But I think aliasing it to ",@" might be a
> little deceptive for people who actually expect destructive splicing.
There's never been a guarantee that it would use destructive splicing
(it's just allowed to), and I generally dislike destructive operations,
so I'd rather not go through extra trouble to support what I tend to see
as a misfeature.
So aliasing ,. to ,@ is OK, but making it work destructively is not.
Stefan
next prev parent reply other threads:[~2015-02-09 3:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 6:39 bug#19790: [PATCH] destructive splicing in backquote Robin Templeton
2015-02-06 15:29 ` Stefan Monnier
2015-02-07 18:51 ` Robin Templeton
2015-02-07 21:46 ` Robin Templeton
2015-02-08 19:23 ` Stefan Monnier
2015-02-08 19:38 ` Artur Malabarba
2015-02-09 3:10 ` Stefan Monnier [this message]
2015-02-09 13:03 ` Artur Malabarba
2016-02-23 11:08 ` Lars Ingebrigtsen
2019-06-25 17:59 ` Lars Ingebrigtsen
2019-06-25 22:52 ` Michael Heerdegen
2019-09-13 23:59 ` Stefan Kangas
2019-09-14 7:15 ` Eli Zaretskii
2019-09-14 12:31 ` Stefan Kangas
2019-09-14 13:30 ` Eli Zaretskii
2019-09-15 14:55 ` Stefan Kangas
2019-09-15 1:46 ` Stefan Monnier
2019-09-15 14:57 ` Stefan Kangas
2019-09-26 16:38 ` Stefan Kangas
2019-09-14 12:07 ` Lars Ingebrigtsen
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=jwvtwyvyecx.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19790@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=robin@terpri.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.