unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Tim Meehan <btmeehan@gmail.com>
To: guile-user@gnu.org
Subject: is there a way to serialize hash tables?
Date: Fri, 25 Dec 2020 21:27:49 -0600	[thread overview]
Message-ID: <CACgrOxJEYB6jL1zThFRmenewqZipFpgzrgSY8zZa4kXzytGXhg@mail.gmail.com> (raw)

I have a big-ish blob of key-value pairs that I would like to not have to
store as text and then convert to a hashtable when I am filtering my data.

Right now I am saving it as an alist and then converting back to a
hashtable using "alist->hashtable" from SRFI 69. I was just hoping that
there was something more clever ... perhaps it is plenty clever enough.


             reply	other threads:[~2020-12-26  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26  3:27 Tim Meehan [this message]
2020-12-26  4:28 ` is there a way to serialize hash tables? John Cowan
2020-12-26 12:10   ` Linus Björnstam
2020-12-27  5:58     ` Tim Meehan
2020-12-29 23:18     ` Aleix Conchillo Flaqué
2020-12-30  8:48       ` Linus Björnstam
2020-12-30 17:19         ` Aleix Conchillo Flaqué
2020-12-26 11:13 ` tomas

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=CACgrOxJEYB6jL1zThFRmenewqZipFpgzrgSY8zZa4kXzytGXhg@mail.gmail.com \
    --to=btmeehan@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).