From: "Linus Björnstam" <linus.internet@fastmail.se>
To: pukkamustard <pukkamustard@posteo.net>,
"Guile User" <guile-user@gnu.org>
Subject: Re: [ANN] Guile SRFI-146 0.1.0 released (purely functional data structures)
Date: Sat, 13 Aug 2022 13:00:42 +0200 [thread overview]
Message-ID: <4ed76087-a17f-46b5-a4fc-ea0c296c9354@www.fastmail.com> (raw)
In-Reply-To: <8635e7869h.fsf@posteo.net>
I remember that Amirouche tried to port this to guile and didn't pass all the SRFI test when using call/ec. He also used my make-coroutine-generator that used delimited continuations.
If you have the time to try it out, many operations could probably gain some Speed by using a coroutine-generator like this: https://git.sr.ht/~bjoli/awesome-coroutine-generators/tree/master/item/awesome-coroutine-generators/base.scm#L64 (where %tag and the generator-end object are replaced to make it compatible with srfi-128 and self-contained).
--
Linus Björnstam
On Mon, 8 Aug 2022, at 10:38, pukkamustard wrote:
> Hello Guilers,
>
> I'm pleased to announce Guile SRFI-146 0.1.0:
> https://inqlab.net/git/guile-srfi-146.git/tag/?h=v0.1.0
>
> Guile SRFI 146 provides bindings to SRFI 146 (Mappings). SRFI 146
> provides two purely functional mapping data structures: One that uses an
> ordering of keys and another that uses a hash on keys. The
> implementations use red-black trees and hash array mapped tries (HAMT).
>
> The library re-uses the SRFI sample implementation with some minor Guile
> specific fixes and optimiztions. The SRFI test suite has also been
> ported.
>
> The package has been submitted to Guix so you should be able to start
> some purely functional hacking very soon
> (https://issues.guix.gnu.org/57055).
>
> Bug reports, fixes and patches are very welcome.
>
> Best regards,
> pukkamustard
next prev parent reply other threads:[~2022-08-13 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:38 [ANN] Guile SRFI-146 0.1.0 released (purely functional data structures) pukkamustard
2022-08-08 17:27 ` Blake Shaw
2022-08-13 11:00 ` Linus Björnstam [this message]
2022-09-24 0:07 ` Aleix Conchillo Flaqué
2022-09-27 8:21 ` pukkamustard
2022-10-23 17:41 ` Aleix Conchillo Flaqué
2022-10-23 17:44 ` Aleix Conchillo Flaqué
2022-11-12 7:32 ` pukkamustard
2022-11-12 15:52 ` Wolf
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=4ed76087-a17f-46b5-a4fc-ea0c296c9354@www.fastmail.com \
--to=linus.internet@fastmail.se \
--cc=guile-user@gnu.org \
--cc=pukkamustard@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.
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).