From: Eli Zaretskii <eliz@gnu.org>
To: schwab@linux-m68k.org
Cc: 37811@debbugs.gnu.org, nicholasdrozd@gmail.com
Subject: bug#37811: "standard GNU Emacs Lisp"
Date: Sat, 19 Oct 2019 15:53:42 +0300 [thread overview]
Message-ID: <83d0es7v6x.fsf@gnu.org> (raw)
In-Reply-To: <83eez87vcz.fsf@gnu.org> (message from Eli Zaretskii on Sat, 19 Oct 2019 15:50:04 +0300)
> Date: Sat, 19 Oct 2019 15:50:04 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 37811@debbugs.gnu.org, nicholasdrozd@gmail.com
>
> > > Common Lisp note: Common Lisp has functions ‘union’ (which avoids
> > > duplicate elements) and ‘intersection’ for set operations.
> > > Although standard GNU Emacs Lisp does not have them, the ‘cl-lib’
> > > library provides versions. *Note (cl)Lists as Sets::.
> > >
> > > So "standard" is used here in contrast to CL. I don't think any of
> > > the proposed replacements pick up that nuance, do they?
> >
> > cl-lib is part of Emacs, but not loaded by default. I think that's what
> > standard is supposed to mean here.
>
> I see your point, but that wasn't my interpretation when I've read
> that text.
>
> Anyway, I think just dropping that word will fix the possible
> confusion.
Or maybe we should simply say this:
Common Lisp note: Common Lisp has functions ‘union’ (which avoids
duplicate elements) and ‘intersection’ for set operations. In Emacs
Lisp, variants of these facilities are provided by the ‘cl-lib’
library. *Note (cl)Lists as Sets::.
next prev parent reply other threads:[~2019-10-19 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 17:11 bug#37811: "standard GNU Emacs Lisp" Nicholas Drozd
2019-10-19 8:37 ` Lars Ingebrigtsen
2019-10-19 9:44 ` Eli Zaretskii
2019-10-19 12:35 ` Andreas Schwab
2019-10-19 12:50 ` Eli Zaretskii
2019-10-19 12:53 ` Eli Zaretskii [this message]
2019-11-07 23:48 ` Stefan Kangas
2019-11-08 9:56 ` 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=83d0es7v6x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37811@debbugs.gnu.org \
--cc=nicholasdrozd@gmail.com \
--cc=schwab@linux-m68k.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 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).