From: ludo@gnu.org (Ludovic Courtès)
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Maintaining implementations of similar utility functions like json-fetch
Date: Mon, 05 Feb 2018 14:12:58 +0100 [thread overview]
Message-ID: <87shafd1gl.fsf@gnu.org> (raw)
In-Reply-To: <CAPsKtfKdPpxW+ctdHtUBfE-MWpjKQzU39M9j2FqD_bwybYxDXA@mail.gmail.com> (Jelle Licht's message of "Wed, 31 Jan 2018 18:32:21 +0100")
Hey,
Jelle Licht <jlicht@fsfe.org> skribis:
> I basically added the robust features of `json-fetch*' to the exported
> `json-fetch'
> instead, and all existing functionality seems to work out as far as I can
> see.
So are you saying that we can get rid of ‘json-fetch*’?
> I did notice that I now produce hash-tables by default, and some of the
> existing usages of `json-fetch*' expect an alist instead. What would be a
> guile-
> appropriate way of dealing with this? I currently have multiple
> `(hash-table->alist (json-fetch <...>))' littered in my patch which seems
> suboptimal,
> but always converting the parsed json into an alist seems like it might
> also not be
> what we want.
Why insist on having an alist? Perhaps you can just stick to hash
tables? :-)
Ludo’.
next prev parent reply other threads:[~2018-02-05 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 15:28 Maintaining implementations of similar utility functions like json-fetch Jelle Licht
2018-01-27 16:09 ` Ludovic Courtès
2018-01-31 17:32 ` Jelle Licht
2018-02-01 11:54 ` Catonano
2018-02-01 12:14 ` Gábor Boskovits
2018-02-05 13:12 ` Ludovic Courtès [this message]
2018-02-05 14:51 ` Alex Vong
2018-06-10 18:50 ` Jelle Licht
2018-06-10 19:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shafd1gl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.