From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Guile Devel <guile-devel@gnu.org>
Subject: Including sjson (formerly (ice-9 json)) and fash.scm in guile proper?
Date: Mon, 08 May 2017 18:17:01 -0500 [thread overview]
Message-ID: <87pofj0wia.fsf@dustycloud.org> (raw)
Hello!
So a while ago, David Thompson submitted (ice-9 json) to Guile proper.
A few changes were requested, so it hadn't made it in. In the meanwhile
I began using it for a number of projects. I also added some
modifications and extensions: #nil became 'null for the representation
of null values, the representation got a bit easier to read for deeply
nested lists-of-dicts-of-lists-of-dicts (moved from '(@ (key . val)) to
'(@ (key val)) after some discussion with David Thompson), I added a
pretty printer, and I also added fash support, snarfing fash.scm from
Andy Wingo (I had a number of cases where I had json documents with a
*lot* of key / value pairs and I was operating on them, and being able
to read/write from a constant time datastructure as an option was
needed).
I released this as an independed library, which is even now packaged in
Guix as guile-sjson.
However, I wonder if we should package this in Guile proper. There is
still one issue to resolve iirc, I should add more specific exception
names.
The biggest problem to me seems that we would also want to include
Wingo's fash.scm in Guile proper. Personally, I think this would be a
big win: highly performant immutable hashmaps are desirable (and though
we have vhashes, setting an existing value keeps the old value, and are
not as fast as fashes in my experience).
So:
- Are Guile's developers open to having an (ice-9 fash) module?
- And should I submit (ice-9 json), with my changes?
Thanks!
- Chris
next reply other threads:[~2017-05-08 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 23:17 Christopher Allan Webber [this message]
2017-05-12 19:15 ` Including sjson (formerly (ice-9 json)) and fash.scm in guile proper? Mark H Weaver
2017-05-14 1:30 ` Christopher Allan Webber
2017-05-15 18:35 ` Mark H Weaver
2017-05-15 19:53 ` Christopher Allan Webber
2017-06-20 22:47 ` Mark H Weaver
2017-06-20 23:18 ` Mark H Weaver
2017-06-20 23:50 ` Mark H Weaver
2017-06-22 16:26 ` Christopher Allan Webber
2017-06-03 13:35 ` 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=87pofj0wia.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@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).