From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-json 2.0.0 released
Date: Thu, 20 Dec 2018 01:34:11 -0800 [thread overview]
Message-ID: <CA+XASoUO=TfRDXMgPZb4rU2nHYW6k4mRX1B=wrySUqL3ZXhcKw@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoXDmhRX_=Yas8n=m=fY_cxypJ=xpwGZR=-=9N9pSskoQQ@mail.gmail.com>
On Wed, Dec 19, 2018 at 10:14 AM Aleix Conchillo Flaqué
<aconchillo@gmail.com> wrote:
>
> My guess is that most of the time people build objects with JSON so it
> seems logic to map them to the most convenient way to represent that
> in Scheme which would be alists.
>
> So, I'm really considering switching to alists for objects and vectors
> for arrays.
>
This would be it:
https://github.com/aconchillo/guile-json/commits/switch-to-alist-and-vectors
I'll write some tests and sleep on it more, but I already like it
better than the current state.
Aleix
next prev parent reply other threads:[~2018-12-20 9:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 5:18 guile-json 2.0.0 released Aleix Conchillo Flaqué
2018-12-13 14:30 ` Thompson, David
2018-12-13 16:35 ` John Cowan
2018-12-13 16:56 ` Thompson, David
2018-12-13 17:09 ` John Cowan
2018-12-13 17:33 ` Thompson, David
2018-12-13 18:28 ` John Cowan
2018-12-13 22:48 ` Aleix Conchillo Flaqué
2018-12-14 1:03 ` Aleix Conchillo Flaqué
2018-12-14 2:28 ` John Cowan
2018-12-18 16:45 ` Ludovic Courtès
2018-12-18 18:09 ` Aleix Conchillo Flaqué
2018-12-19 10:48 ` Ludovic Courtès
2018-12-19 18:14 ` Aleix Conchillo Flaqué
2018-12-19 19:17 ` rain1
2018-12-19 20:05 ` John Cowan
2018-12-19 21:13 ` Ludovic Courtès
2018-12-20 9:34 ` Aleix Conchillo Flaqué [this message]
2018-12-20 10:59 ` Ludovic Courtès
2018-12-20 18:09 ` Aleix Conchillo Flaqué
2018-12-29 23:51 ` Aleix Conchillo Flaqué
2018-12-18 23:48 ` rain1
2018-12-19 15:18 ` Arne Babenhauserheide
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='CA+XASoUO=TfRDXMgPZb4rU2nHYW6k4mRX1B=wrySUqL3ZXhcKw@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).