From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Did `inline' used to do something else?
Date: Sun, 19 Nov 2017 14:06:18 -0800 [thread overview]
Message-ID: <87y3n1x6sl.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 861sku0y1h.fsf@zoho.com
Emanuel Berg <moasen@zoho.com> writes:
> Eric Abrahamsen wrote:
>
>>> By the way it is interesting that Gnus is
>>> what brought this issue up to date because
>>> Gnus (or Emacs Lisp) has speed issues and
>>> one way in Gnus to counteract it is the
>>> presence of very long functions.
>>
>> My observation so far is that Gnus has lots
>> of this sort of micro-optimization, but that
>> much of the slowness comes from how the
>> larger routines and data structures work.
>> In fairness, we have a lot of tools now that
>> weren't present when Gnus was written.
>
> With respect to data structures? What tools
> are those?
Mostly real hash tables, and object classes. I suspect using those will
make things go a bit faster -- at the very least it will reduce the
amount of boilerplate code.
It's possible that threading will provide some speedups, but I'm not
certain.
We'll see! My main goals is making the code more readable and
maintainable, but hopefully some speed improvements will come out of
that as well.
next prev parent reply other threads:[~2017-11-19 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 21:14 Did `inline' used to do something else? Eric Abrahamsen
2017-11-19 0:05 ` Emanuel Berg
2017-11-19 0:38 ` Eric Abrahamsen
2017-11-19 2:01 ` Emanuel Berg
2017-11-19 5:59 ` Eric Abrahamsen
2017-11-19 9:53 ` Joost Kremers
2017-11-19 10:00 ` Joost Kremers
2017-11-19 15:01 ` Emanuel Berg
2017-11-19 16:02 ` Michael Heerdegen
2017-11-19 17:17 ` Emanuel Berg
2017-11-19 20:48 ` Eric Abrahamsen
2017-11-19 21:16 ` Emanuel Berg
2017-11-19 22:06 ` Eric Abrahamsen [this message]
2017-11-19 22:51 ` Emanuel Berg
2017-11-20 3:56 ` Emanuel Berg
2017-11-20 4:04 ` Emanuel Berg
2017-11-20 19:31 ` Michael Heerdegen
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=87y3n1x6sl.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.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 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.