From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Henry Minsky <henry.minsky@gmail.com>,
45032@debbugs.gnu.org
Subject: bug#45032: 26.3; json-pretty-print of JSON with dict containing 't' as a key causes error
Date: Sun, 06 Dec 2020 14:37:40 +0100 [thread overview]
Message-ID: <87tuszcaxn.fsf@gnus.org> (raw)
In-Reply-To: <CAArVCkQFTR7yxT83cm23noF5SLk_Oz41D6+w3d8fJALyyexyOg@mail.gmail.com> (Philipp Stephani's message of "Sat, 5 Dec 2020 20:35:42 +0100")
Philipp Stephani <p.stephani2@gmail.com> writes:
>> I think it's important that native and Elisp JSON serialisation are as
>> consistent as possible here;
>
> I don't think that's realistic: any change in behavior to either of
> these functions would be a breaking change.
I think we should have JSON/Elisp round trips that are 100%
reproducible. The current functions certainly aren't.
But we could just leave them as deprecated legacy functions and
introduce new ones that are consistent.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-06 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:19 bug#45032: 26.3; json-pretty-print of JSON with dict containing 't' as a key causes error Henry Minsky
2020-12-04 10:15 ` Lars Ingebrigtsen
2020-12-05 16:17 ` Basil L. Contovounesios
2020-12-05 19:35 ` Philipp Stephani
2020-12-05 22:13 ` Basil L. Contovounesios
2020-12-06 13:37 ` Lars Ingebrigtsen [this message]
2020-12-06 17:02 ` Philipp Stephani
2020-12-06 17:06 ` Lars Ingebrigtsen
2020-12-06 17:16 ` Philipp Stephani
2020-12-07 13:39 ` Lars Ingebrigtsen
[not found] ` <CAJo0r8gbrVk2wZatYS6_G7+7+tF_7VHO9KffrEMWanOK5BjuUg@mail.gmail.com>
2020-12-08 13:26 ` Lars Ingebrigtsen
2020-12-06 19:26 ` Dmitry Gutov
2020-12-12 14:28 ` Philipp Stephani
2020-12-12 21:25 ` Dmitry Gutov
2020-12-13 13:19 ` Philipp Stephani
2020-12-13 18:58 ` Dmitry Gutov
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=87tuszcaxn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45032@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=henry.minsky@gmail.com \
--cc=p.stephani2@gmail.com \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.