From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Philipp Stephani <phst@google.com>,
41946@debbugs.gnu.org, yyoncho <yyoncho@gmail.com>
Subject: bug#41946: 27.0.91; native json parsing: add :empty-object configuration
Date: Wed, 04 Aug 2021 07:55:04 +0200 [thread overview]
Message-ID: <8735rpiwjr.fsf@gnus.org> (raw)
In-Reply-To: <05291961-8810-c805-bc29-88dfcc8206ad@yandex.ru> (Dmitry Gutov's message of "Mon, 2 Aug 2021 02:53:56 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 31.07.2021 19:12, Lars Ingebrigtsen wrote:
>> You can wrap the json calls with a function that flips nil/:empty-object
>> easy enough, can't you?
>
> By copying the object tree and substituting nil for something else
> recursively?
>
> That says "more GC" to me, which can be a problem when the structure
> is big enough.
The user didn't want to rewrite the code to alter some conditionals, and
instead wanted Emacs to be changed so that they didn't have to do that.
I pointed out that the user can trivially just pre-process the data if
they didn't want to rewrite those conditionals.
(And they can just modify the structure in place if GC's a concern.)
I think the conclusion here is that we don't want to add :empty-object
to json.c, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-04 5:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 5:52 bug#41946: 27.0.91; native json parsing: add :empty-object configuration Ivan Yonchovski
2020-06-19 7:29 ` Eli Zaretskii
2020-06-19 8:07 ` yyoncho
2021-07-31 15:07 ` Lars Ingebrigtsen
2021-07-31 15:51 ` yyoncho
2021-07-31 16:12 ` Lars Ingebrigtsen
2021-08-01 23:53 ` Dmitry Gutov
2021-08-04 5:55 ` Lars Ingebrigtsen [this message]
2021-08-04 10:54 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735rpiwjr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=41946@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=phst@google.com \
--cc=yyoncho@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).