Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125359
Precedence: bulk
MIME-Version: 1.0 (Mimestream 1.3.8)
References: <CAGKNXQGahmJ8nHVy1C8d7B=Zf-jse0U6KkNBeSijDJHgbJet1Q@mail.gmail.com>
 <bccecc0d-f771-4cbb-9bfb-b66e41baa9cf@Spark>
In-Reply-To: <bccecc0d-f771-4cbb-9bfb-b66e41baa9cf@Spark>
Date: Fri, 30 Aug 2024 03:21:14 -0700
Message-ID: <CAGKNXQEcytwVxSBwWwjJE7A-E500MnuHZpMPg=m1Q+8fq1E7Ug@mail.gmail.com>
Subject: Re: [PHP-DEV] json_encode() and Generators / RFC Karma
To: John Coggeshall <john@coggenterprises.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000007953c60620e3f33e"
From: phofstetter@sensational.ch (Philip Hofstetter)

--0000000000007953c60620e3f33e
Content-Type: text/plain; charset="UTF-8"

 Hi John,


On Aug 30, 2024 at 09:42:05, John Coggeshall <john@coggenterprises.com>
wrote:

> This seems entirely reasonable and I would welcome an RFC for it (unless
> someone has a better idea as to how to handle this case).
>
>
The other options I considered were to either materialize the Generator,
but given that they can run indefinitely this seems very dangerous or
json-encoding them as [] but that would be lying in most cases, so doing
what serialize() does felt like the only sensible option and would prevent
a nasty case of silent failure.

Regards

Philip

--0000000000007953c60620e3f33e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><body><div dir=3D"ltr">
    Hi John,</div><div dir=3D"ltr"><br></div>
<br>
<div class=3D"gmail_quote">
    <div dir=3D"ltr" class=3D"gmail_attr">On Aug 30, 2024 at 09:42:05, John=
 Coggeshall &lt;<a href=3D"mailto:john@coggenterprises.com">john@coggenterp=
rises.com</a>&gt; wrote:<br></div>
    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex" type=3D"cite">
        <div>
<div>
<title></title>
</div>
<div>
<div name=3D"messageBodySection">
<div dir=3D"auto">This seems entirely reasonable and I would welcome an RFC=
 for it (unless someone has a better idea as to how to handle this case).<b=
r>
<br></div></div></div></div></blockquote></div><div class=3D"gmail_signatur=
e" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><br></div><div =
dir=3D"ltr">The other options I considered were to either materialize the G=
enerator, but given that they can run indefinitely this seems very dangerou=
s or json-encoding them as [] but that would be lying in most cases, so doi=
ng what serialize() does felt like the only sensible option and would preve=
nt a nasty case of silent failure.</div><div dir=3D"ltr"><br></div><div dir=
=3D"ltr">Regards</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Philip</d=
iv></div></div></body></html>

--0000000000007953c60620e3f33e--