From: Nicolas Petton <nicolas@petton.fr>
To: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Tom Tromey <tom@tromey.com>, emacs-devel@gnu.org
Subject: RE: map-put! and (setf (map-elt ...) ..) on lists
Date: Tue, 18 Dec 2018 17:34:59 +0100 [thread overview]
Message-ID: <871s6en68c.fsf@petton.fr> (raw)
In-Reply-To: <150bbe9c-3ef4-4d43-9fce-23d608abd829@default>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Drew Adams <drew.adams@oracle.com> writes:
>> > Do we have a non-destructive `map-put'?
>>
>> There's `map-insert'.
>
> My point was that there is no need for a function
> name to signal that the function so named is
> "destructive". The doc string should do that,
> however.
It can be very important to know that a function is destructive, I don't
think it's a should be seen as an internal detail of the function. IOW,
I think that whether a function is destructive or not is part of what
the function does, not how it does it.
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-12-18 16:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:32 map-put! and (setf (map-elt ...) ..) on lists Stefan Monnier
2018-12-16 16:32 ` Tom Tromey
2018-12-16 17:37 ` Drew Adams
2018-12-16 18:20 ` Stefan Monnier
2018-12-16 23:06 ` Tom Tromey
2018-12-17 3:16 ` Stefan Monnier
2018-12-17 4:08 ` Stefan Monnier
2018-12-17 11:41 ` Nicolas Petton
2018-12-17 16:06 ` Eli Zaretskii
2018-12-17 16:07 ` Drew Adams
2018-12-18 10:11 ` Nicolas Petton
2018-12-18 13:56 ` Stefan Monnier
2018-12-18 15:42 ` Drew Adams
2018-12-18 15:34 ` Drew Adams
2018-12-18 15:47 ` Stefan Monnier
2018-12-18 16:34 ` Nicolas Petton [this message]
2018-12-18 17:41 ` Drew Adams
2018-12-18 20:44 ` Nicolas Petton
2018-12-16 18:21 ` Stefan Monnier
2018-12-17 11:38 ` Nicolas Petton
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=871s6en68c.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=tom@tromey.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).