From: "Thompson, David" <dthompson2@worcester.edu>
To: pukkamustard <pukkamustard@posteo.net>
Cc: Jessica Tallon <tsyesika@tsyesika.se>, guile-devel <guile-devel@gnu.org>
Subject: Re: Functional datatypes in Guile
Date: Tue, 28 Feb 2023 11:04:36 -0500 [thread overview]
Message-ID: <CAJ=RwfYdTLdKyEu2embKFa_ixwZ--rpQsHYjaM-=Q2vKq9oOmg@mail.gmail.com> (raw)
In-Reply-To: <86bklenq75.fsf@posteo.net>
Hi pukkamustard,
On Tue, Feb 28, 2023 at 3:34 AM pukkamustard <pukkamustard@posteo.net> wrote:
>
>
> I've been using SRFI-146
> (https://srfi.schemers.org/srfi-146/srfi-146.html) for functional
> mappings. There's a Guile port:
> https://inqlab.net/git/guile-srfi-146.git/ (also in Guix -
> guile-srfi-146).
Your Guile port of (srfi srfi-146 hash) looks really nice! A
functional hash is the most important data structure for our needs at
Spritely. Do you know if it's thread-safe (unlike vhashes)? Andy's
fash implementation uses atomic boxes, for example.
Also, what are your thoughts on read syntax? I find myself using
alists more often than I probably should because the syntax is
pleasant. (hashmap comparator 'foo 1 'bar 2) is... okay, but terse
syntax for the common case of a hash with literal keys would be nice.
For example, #hq((foo 1) (bar 2)) for a hash with keys compared with
eq? Scheme is kind of odd for not having hash literal syntax.
> I've previously used pfds (as mentioned by Maxime), but I've encountered
> some nasty issues that are keeping me from using it again
> (https://github.com/ijp/pfds/issues/5).
Good to know about this issue, thanks!
- Dave
next prev parent reply other threads:[~2023-02-28 16:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 13:17 Functional datatypes in Guile Jessica Tallon
2023-02-28 7:47 ` Maxime Devos
2023-02-28 8:22 ` pukkamustard
2023-02-28 16:04 ` Thompson, David [this message]
2023-02-28 16:54 ` Philip McGrath
2023-03-04 16:38 ` pukkamustard
2023-03-05 12:58 ` Linus Björnstam
2023-03-07 15:02 ` pukkamustard
2023-06-10 16:47 ` Ludovic Courtès
2023-06-10 18:28 ` Dr. Arne Babenhauserheide
2023-06-16 5:15 ` pukkamustard
2023-06-21 21:53 ` Ludovic Courtès
2023-02-28 17:03 ` Clojure support Lassi Kortela
2023-03-04 10:28 ` Linus Björnstam
2023-03-04 11:22 ` Philip McGrath
2023-05-07 15:36 ` Linus Björnstam
2023-05-13 22:10 ` Rob Browning
2023-05-20 9:36 ` Maxime Devos
2023-05-21 2:29 ` Rob Browning
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='CAJ=RwfYdTLdKyEu2embKFa_ixwZ--rpQsHYjaM-=Q2vKq9oOmg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guile-devel@gnu.org \
--cc=pukkamustard@posteo.net \
--cc=tsyesika@tsyesika.se \
/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).