From: "Linus Björnstam" <linus.internet@fastmail.se>
To: "Amirouche Boubekki" <amirouche.boubekki@gmail.com>,
"Guile User" <guile-user@gnu.org>
Subject: Re: Raising awareness about guile-pfds status
Date: Mon, 15 Jul 2019 22:50:05 +0200 [thread overview]
Message-ID: <6adde1b2-4967-458c-a688-e36b349b4cd1@www.fastmail.com> (raw)
In-Reply-To: <CAL7_Mo_MQshyXkL99YypK02HsELkwbVU+dR9h1h1yVtLc8AxYg@mail.gmail.com>
If it is HAMTs or persistent vectors you want, I have a git repo of Andy's Fash and Fector (functional hashmaps and functional.vectors). Fash lacks some parts to become a fast implementation of (srfi 146 hash), like being able to properly delete keys. I would implement it myself if I had any friggin idea what the code did, but to my limited mind it is quite impenetrable.
Other than that, I have a decently fast implementation of a pairing heap in my Nietzsche repo, which I found is generally slightly faster than the height balanced leftist tree in the PFDS library (and, should be said, about an order of magnitude slower than a regular binary heap using vectors).
The Fector library: https://bitbucket.org/bjoli/guile-fector
The fash library: https://bitbucket.org/bjoli/guile-fash/
My pairing heap: https://bitbucket.org/bjoli/nietzsche/src/default/data/pairing-heap.scm
I don't know how using records compares to using cons pairs in guile, but there might be some speed gains. It also lacks a proper (as in fast) list->node because my 23 year old me didn't know how to implement it. It should be trivial.
Fash and Fector are very fast. Andy likes speed :)
--
Linus Björnstam
On Mon, 15 Jul 2019, at 18:06, Amirouche Boubekki wrote:
> The original maintainer of guile-pfds is sadly not responding to my mails.
>
> Right now, guile-pfds is the goto solution for functional data structures
> in Guile,
> and prolly other Scheme implementations.
>
> At least the hamt has a bug, see https://github.com/ijp/pfds/pull/6/files
>
> I think this is a very important package especially for guile that doesn't
> have a functional hashmaps.
>
> Anyone willing to take ownership of the project?
>
>
> ref: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35518
>
> --
> Amirouche ~ amz3 ~ https://hyper.dev
>
next prev parent reply other threads:[~2019-07-15 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 16:05 Raising awareness about guile-pfds status Amirouche Boubekki
2019-07-15 18:38 ` Nala Ginrut
2019-07-15 20:50 ` Linus Björnstam [this message]
2019-07-15 21:19 ` John Cowan
2019-07-16 7:07 ` Linus Björnstam
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=6adde1b2-4967-458c-a688-e36b349b4cd1@www.fastmail.com \
--to=linus.internet@fastmail.se \
--cc=amirouche.boubekki@gmail.com \
--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).