unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Linus Björnstam" <linus.internet@fastmail.se>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: is there a way to serialize hash tables?
Date: Wed, 30 Dec 2020 09:48:15 +0100	[thread overview]
Message-ID: <bf77f119-e7ef-4582-87f6-2e655555d57f@www.fastmail.com> (raw)
In-Reply-To: <CA+XASoXLfSPzgwrsir8qOqb_zdw=ZKyX1y2sTp0sj8w6bd9+Rw@mail.gmail.com>

I have added it to my phone's dictionary, but for some reason it still autocorrects to Alex. Sorry about that. I know very well that it is Aleix.

I remember I had the same problem last time.

-- 
  Linus Björnstam

On Wed, 30 Dec 2020, at 00:18, Aleix Conchillo Flaqué wrote:
> You almost got it right Linus, it's Aleix. :-)
> 
> For the curious, it sounds something like "Alaish" or here in the US 
> most people can pronounce it as "Alesh". But more accurately [aleʃ] 
> (https://en.m.wikipedia.org/wiki/Help:IPA/Catalan)
> 
> Anyways, happy hacking and happy New Year to everyone!
> 
> Aleix
> 
> On Sat, Dec 26, 2020, 4:10 AM Linus Björnstam 
> <linus.internet@fastmail.se> wrote:
> > Alex and I got the speed of guile-json up to about 19megs a second under guile 3 on a 4 year old intel i5, which may or may not be adequate for your needs, Tim.
> > 
> > I have some code I wrote during that spurt that preforms slightly better than guile-json in general (about 3-4% on my machine. Alex could not repeat those numbers) an on files with many large strings in particular (10% in extreme cases).  If that is interesting I could put it online somewhere. The functioning code is a derivate work of guile-json, so the GPL applies.
> > 
> > -- 
> >   Linus Björnstam
> > 
> > On Sat, 26 Dec 2020, at 05:28, John Cowan wrote:
> > > I think that's the best bet, although JSON is also a possibility.  I'm
> > > working on a more general text-serialization solution, but it will be quite
> > > some time before I have a chance to work on it.
> > > 
> > > On Fri, Dec 25, 2020 at 10:28 PM Tim Meehan <btmeehan@gmail.com> wrote:
> > > 
> > > > 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-30  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26  3:27 is there a way to serialize hash tables? Tim Meehan
2020-12-26  4:28 ` 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 [this message]
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=bf77f119-e7ef-4582-87f6-2e655555d57f@www.fastmail.com \
    --to=linus.internet@fastmail.se \
    --cc=aconchillo@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).