From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>,
Michael Heerdegen <michael_heerdegen@web.de>,
emacs-devel@gnu.org
Subject: Re: master 4b79c80c999 1/2: New function 'sort-on'
Date: Thu, 7 Mar 2024 03:34:12 +0200 [thread overview]
Message-ID: <a6b91fbf-b98d-4f2e-bbc9-4512b01a251d@gutov.dev> (raw)
In-Reply-To: <m2h6hjqfuh.fsf@newartisans.com>
On 06/03/2024 22:12, John Wiegley wrote:
>>>>>> Dmitry Gutov<dmitry@gutov.dev> writes:
>> Here's a version from Daniel as well:
> This version from Daniel looks pretty optimal to me. It trades building a
> whole new list spine that is sent to GC, for an extra O(n) traversal to
> “restore” each of the original list cells. Done in C, I have a feeling that
> would beat the GC.
Speed-wise, IIRC this version already beats the committed implementation.
I'm talking about moving to C in the context of merging this feature
with the basic 'sort' function. Because it really looks more fitting for
a new optional argument now, rather than a separate function.
next prev parent reply other threads:[~2024-03-07 1:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170688047526.14693.2994051491358257471@vcs2.savannah.gnu.org>
[not found] ` <20240202132756.4272CC0EFE7@vcs2.savannah.gnu.org>
2024-02-02 15:00 ` master 4b79c80c999 1/2: New function 'sort-on' Daniel Mendler via Emacs development discussions.
2024-02-02 15:04 ` Eli Zaretskii
2024-02-02 15:26 ` Daniel Mendler via Emacs development discussions.
2024-02-02 15:47 ` Eli Zaretskii
2024-02-02 16:05 ` Daniel Mendler via Emacs development discussions.
2024-02-05 12:14 ` Michael Heerdegen
2024-02-02 15:55 ` Dmitry Gutov
2024-02-02 15:30 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 15:35 ` Daniel Mendler via Emacs development discussions.
2024-02-02 16:08 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 16:23 ` Daniel Mendler via Emacs development discussions.
2024-02-02 16:43 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 15:50 ` Eli Zaretskii
2024-02-02 16:06 ` Eshel Yaron
2024-02-02 16:34 ` Eli Zaretskii
2024-02-02 16:46 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 17:55 ` Emanuel Berg
2024-02-05 0:48 ` Dmitry Gutov
2024-02-05 5:30 ` Yuri Khan
2024-02-05 12:52 ` Eli Zaretskii
2024-02-05 13:25 ` Dmitry Gutov
2024-02-05 14:31 ` Eli Zaretskii
2024-02-05 14:47 ` Dmitry Gutov
2024-02-05 15:10 ` Eli Zaretskii
2024-02-05 15:29 ` Dmitry Gutov
2024-02-28 7:40 ` Michael Heerdegen
2024-03-01 23:37 ` Dmitry Gutov
2024-03-04 6:45 ` Michael Heerdegen
2024-03-04 16:43 ` Dmitry Gutov
2024-03-05 8:06 ` Michael Heerdegen
2024-03-05 10:21 ` Michael Heerdegen via Emacs development discussions.
2024-03-05 12:39 ` Eli Zaretskii
2024-03-06 3:20 ` Michael Heerdegen
2024-03-06 12:10 ` Eli Zaretskii
2024-03-06 18:34 ` Dmitry Gutov
2024-03-06 20:12 ` John Wiegley
2024-03-07 1:34 ` Dmitry Gutov [this message]
2024-03-05 12:44 ` Dmitry Gutov
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=a6b91fbf-b98d-4f2e-bbc9-4512b01a251d@gutov.dev \
--to=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).