From: "Mattias Engdegård" <mattiase@acm.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Philip Kaludercic <philipk@posteo.net>,
Lynn Winebarger <owinebar@gmail.com>,
Matthew Trzcinski <matt@excalamus.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [elpa] externals/org 26ef5e3e5b: org-src: Use `sh-mode' for all the shells it can handle
Date: Mon, 17 Apr 2023 20:33:40 +0200 [thread overview]
Message-ID: <8E317554-E278-446B-B5F9-7FA97F97D63F@acm.org> (raw)
In-Reply-To: <jwv4jpe76p5.fsf-monnier+emacs@gnu.org>
17 apr. 2023 kl. 19.37 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
>> (cons X1 ... (cons Xn Y)...)
>>
>> into
>>
>> (nconc (list X1 ... Xn) Y)
>
> Hmm.., turning a pure expression into a (internally) side-effecting one?
The transform would have to be made at a low enough level where purity no longer matters, perhaps in codegen. (Until we get a GC that penalises mutation.)
> How 'bout adding&using `list*` instead?
I wouldn't mind adding `list*` at all. (It would eventually compile to list + nconc, of course.)
We could make backquote emit `list*` and avoid stack overflow problems of the sort that was mentioned earlier (or maybe it was something else).
next prev parent reply other threads:[~2023-04-17 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168174708495.14139.12756054653439048176@vcs2.savannah.gnu.org>
[not found] ` <20230417155805.3E200C1391A@vcs2.savannah.gnu.org>
2023-04-17 16:08 ` [elpa] externals/org 26ef5e3e5b: org-src: Use `sh-mode' for all the shells it can handle Stefan Monnier
2023-04-17 16:16 ` Lynn Winebarger
2023-04-17 16:27 ` Philip Kaludercic
2023-04-17 16:37 ` Andreas Schwab
2023-04-17 16:42 ` Philip Kaludercic
2023-04-17 16:39 ` Mattias Engdegård
2023-04-17 16:47 ` Mattias Engdegård
2023-04-17 17:37 ` Stefan Monnier
2023-04-17 18:33 ` Mattias Engdegård [this message]
2023-04-17 20:08 ` Stefan Monnier
2023-04-18 9:50 ` Mattias Engdegård
2023-04-17 17:11 ` Stefan Monnier
2023-04-17 17:24 ` Lynn Winebarger
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=8E317554-E278-446B-B5F9-7FA97F97D63F@acm.org \
--to=mattiase@acm.org \
--cc=emacs-devel@gnu.org \
--cc=matt@excalamus.com \
--cc=monnier@iro.umontreal.ca \
--cc=owinebar@gmail.com \
--cc=philipk@posteo.net \
/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.