From: Robert Boyer <robertstephenboyer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Simon Leinen <simon.leinen@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Some thoughts about Emacs performance
Date: Mon, 19 Feb 2024 13:05:28 -0600 [thread overview]
Message-ID: <CAP9n0TP2WgaSrgerd48C6nqiNjhE4c3gFjaipGOurZm4O8dniQ@mail.gmail.com> (raw)
In-Reply-To: <87zfvweiy6.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
> Another option might be contributing to Emacs C sources.
Surely you're joking, Mr. Feynman. 1. sort in Emacs is, I do believe,
written in C and seems ok, but could be improved. 2. You probably cannot
imagine, in this day, how totally ignorant I am of C! It is unforgivable.
> it is not yet clear how long it will take to implement type declaration
support.
My bet is that it will be a long time coming, from the vibes I get. But
what do I know?
Bob
On Mon, Feb 19, 2024 at 6:25 AM Ihor Radchenko <yantar92@posteo.net> wrote:
> Robert Boyer <robertstephenboyer@gmail.com> writes:
>
> > I say I fear for the worst because if that bug is what I think it is, it
> > would kill 'msa' performance.
> > Very secondarily, even if the bug is fixed, I have no idea how I could
> ever
> > take advantage of it!
>
> As Andrea mentioned in
> https://yhetil.org/emacs-devel/yp1cyssanrp.fsf@fencepost.gnu.org/, type
> declarations are not yet supported and it is not yet clear how long it
> will take to implement type declaration support.
>
> If you wish to contribute a better sorting to Emacs, another option
> might be contributing to Emacs C sources. Check out src/sort.c file
> (tim_sort) for the sort implementation that is currently in use.
> https://git.savannah.gnu.org/cgit/emacs.git/tree/src/sort.c#n915
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
--
Anything I seem to state should be taken as a question. I am at least 77
and feeble.
[-- Attachment #2: Type: text/html, Size: 2830 bytes --]
next prev parent reply other threads:[~2024-02-19 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 5:44 Some thoughts about Emacs performance Robert Boyer
2024-02-08 14:47 ` Ihor Radchenko
2024-02-16 14:08 ` Simon Leinen
2024-02-16 16:15 ` Robert Boyer
2024-02-19 12:29 ` Ihor Radchenko
2024-02-19 19:05 ` Robert Boyer [this message]
2024-02-16 16:31 ` Robert Boyer
2024-02-16 18:06 ` Robert Boyer
2024-02-16 20:28 ` [External] : " Drew Adams
2024-02-16 18:34 ` Robert Boyer
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 23:53 Arthur Miller
[not found] <DU2PR02MB10109962DC3D994DCE1BCC11896442@DU2PR02MB10109.eurprd02.prod.outlook.com>
2024-02-09 0:23 ` Ihor Radchenko
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=CAP9n0TP2WgaSrgerd48C6nqiNjhE4c3gFjaipGOurZm4O8dniQ@mail.gmail.com \
--to=robertstephenboyer@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=simon.leinen@gmail.com \
--cc=yantar92@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 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).