unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Linus Björnstam" <linus.internet@fastmail.se>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user <guile-user@gnu.org>
Subject: Re: guile-json 4.2.0 released
Date: Thu, 2 Jul 2020 17:10:28 -0700	[thread overview]
Message-ID: <CA+XASoX+VcadM0azBbF2qPcJ5NocrAV-gr58b1YpfRn6gXmn6w@mail.gmail.com> (raw)
In-Reply-To: <1d839cb5-86d9-4fe4-b2c4-e3c985537cbc@www.fastmail.com>

Hi!

I briefly looked at srfi-180, it seems I could take guile-json internals to
implement that srfi-180 API and then implement current guile-json API on
top of that. It would be nice to still support both.

Maybe I will give it a try at some point in the near future.

Aleix

On Thu, Jul 2, 2020 at 9:24 AM Linus Björnstam <linus.internet@fastmail.se>
wrote:

> With the current api, no. The code of guile-json could be used to
> implement srfi-180, but the current guile-json API could not efficiently
> implement srfi-180.
>
> I am not Aleix, but I helped making it faster for the 4.0 release.
>
> --
>   Linus Björnstam
>
> On Thu, 2 Jul 2020, at 16:55, Bill Markmann wrote:
> > It looks like the surface API is different, but the internal json <-->
> > scheme records functionality overlaps... Any thoughts on whether
> > guile-json  would serve as the underpinnings of an implementation of
> > srfi-180?
> >
> > https://srfi.schemers.org/srfi-180/srfi-180.html
> >
> > https://github.com/scheme-requests-for-implementation/srfi-180
> >
> > - Bill
> >
> > On Thu, Jul 2, 2020 at 9:08 AM Ludovic Courtès <ludo@gnu.org> wrote:
> >
> > > Hi,
> > >
> > > Aleix Conchillo Flaqué <aconchillo@gmail.com> skribis:
> > >
> > > > * Changes since 4.1.0
> > > >
> > > > https://github.com/aconchillo/guile-json/blob/master/NEWS
> > >
> > > --8<---------------cut here---------------start------------->8---
> > >  - Introduce (define-json-mapping) which allows converting a JSON
> object
> > > into
> > >     a record type and vice versa. The initial code for this feature was
> > > copied
> > >     from the GNU Guix project.
> > > --8<---------------cut here---------------end--------------->8---
> > >
> > > Nice!  :-)
> > >
> > > There’s a bidirectional version here, but it’s slightly incompatible:
> > >
> > >
> > >
> https://gitlab.inria.fr/guix-hpc/guix-kernel/-/blob/master/jupyter/json.scm
> > >
> > > It relies on (guix records), which is not great for Guile-JSON.
> > >
> > > Ludo’.
> > >
> > >
> > >
> >
>
>


  reply	other threads:[~2020-07-03  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  7:26 guile-json 4.2.0 released Aleix Conchillo Flaqué
2020-06-30 20:58 ` Zelphir Kaltstahl
2020-07-02 13:07 ` Ludovic Courtès
2020-07-02 14:55   ` Bill Markmann
2020-07-02 15:55     ` Nala Ginrut
2020-07-02 16:10     ` Linus Björnstam
2020-07-03  0:10       ` Aleix Conchillo Flaqué [this message]
2020-07-04  6:13   ` Aleix Conchillo Flaqué
2020-07-04 19:50     ` Ludovic Courtès

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+XASoX+VcadM0azBbF2qPcJ5NocrAV-gr58b1YpfRn6gXmn6w@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=linus.internet@fastmail.se \
    --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).