From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: list vs vector
Date: Wed, 28 Dec 2022 15:34:18 +0100 [thread overview]
Message-ID: <Y6xT6nd6/uSMmf+k@tuxteam.de> (raw)
In-Reply-To: <CAGUt3y4ASWsVtVdduiRD99tZ1iDF97vvtmf3h_xi1UnyZcTNKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Wed, Dec 28, 2022 at 02:22:16PM +0100, Sascha Ziemann wrote:
> I spent my Christmas vacation playing with XML and tree traversal. And
> I have observed some strange timings, while measuring the execution
> time of different algorithms. My test file is the XCB XML schema:
[vector version slightly slower than lists]
This is interesting. Have you tried profiling? Sometimes it's as
easy as saying ,profile (my expression) at the Guile repl.
(I'm not looking into the code, since I try to avoid Github when
I can).
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-28 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 13:22 list vs vector Sascha Ziemann
2022-12-28 14:34 ` tomas [this message]
2022-12-28 18:29 ` Damien Mattei
2022-12-28 20:23 ` Olivier Dion via General Guile related discussions
2022-12-29 9:43 ` Sascha Ziemann
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y6xT6nd6/uSMmf+k@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@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.
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).