From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16963@debbugs.gnu.org, Demetrios Obenour <demetriobenour@gmail.com>
Subject: bug#16963: A patch to create a list-with-tail primitive.
Date: Thu, 27 Jun 2019 20:30:27 -0700 (PDT) [thread overview]
Message-ID: <7c902ff5-10cb-467c-b5ed-bf9d4df8cf71@default> (raw)
In-Reply-To: <87v9wq5rl4.fsf@gmail.com>
> Oh, this reminds me I had started writing a patch for this. I used the
> name cons* instead of list* though, I always found it more logical:
> cons* is cons repeated, just like let* is let repeated. Let me dust it
> off:
The name has long been `list*' in Lisp, including
in Common Lisp. That's the name that should (still)
be used, IMO.
http://clhs.lisp.se/Body/f_list_.htm
list* is like list except that the last argument to list
becomes the car of the last cons constructed, while the
last argument to list* becomes the cdr of the last cons
constructed. Hence, any given call to list* always
produces one fewer conses than a call to list with the
same number of arguments.
If the last argument to list* is a list, the effect is
to construct a new list which is similar, but which has
additional elements added to the front corresponding to
the preceding arguments of list*.
If list* receives only one object, that object is returned,
regardless of whether or not it is a list.
prev parent reply other threads:[~2019-06-28 3:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:58 bug#16963: A patch to create a list-with-tail primitive Demetrios Obenour
2014-03-25 2:10 ` Stefan
2014-03-25 2:45 ` Daniel Colascione
2014-03-27 23:37 ` Demetrios Obenour
2014-03-27 23:38 ` Daniel Colascione
2014-03-28 0:43 ` Demetrios Obenour
2014-03-29 1:46 ` Demetrios Obenour
2014-03-29 1:48 ` Daniel Colascione
2014-03-29 13:30 ` Demetrios Obenour
2016-02-24 2:51 ` Lars Ingebrigtsen
2019-06-26 14:30 ` Lars Ingebrigtsen
2019-06-28 3:14 ` Noam Postavsky
2019-06-28 3:30 ` Drew Adams [this message]
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=7c902ff5-10cb-467c-b5ed-bf9d4df8cf71@default \
--to=drew.adams@oracle.com \
--cc=16963@debbugs.gnu.org \
--cc=demetriobenour@gmail.com \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.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 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.