Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130359
Precedence: list
MIME-Version: 1.0
References: <CALaXqqRaZRefdqq1=R_hiuGfesOAnwhcC=RwYXLzykYQ2rodgQ@mail.gmail.com>
 <CAPyj-LDYQX57Y4okTg8MJvi+5WnOt_ULN6dY=ZmicApC5jKwBg@mail.gmail.com>
In-Reply-To: <CAPyj-LDYQX57Y4okTg8MJvi+5WnOt_ULN6dY=ZmicApC5jKwBg@mail.gmail.com>
Date: Sun, 15 Mar 2026 11:04:25 -0700
Message-ID: <CALaXqqTUN+qrALGmEsCDNZqkBLrHe318qCXc+2bHAu0JfrNuUw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Debugable enums
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000dbe1b1064d13f053"
From: daniel.e.scherzer@gmail.com (Daniel Scherzer)

--000000000000dbe1b1064d13f053
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Mar 15, 2026 at 11:01=E2=80=AFAM Ilija Tovilo <tovilo.ilija@gmail.c=
om>
wrote:

> Hi Daniel
>
> On Fri, Mar 13, 2026 at 1:06=E2=80=AFAM Daniel Scherzer
> <daniel.e.scherzer@gmail.com> wrote:
> >
> > I'd like to start the discussion for a new RFC about removing the
> prohibition on __debugInfo() methods on enums.
> >
> > * RFC: https://wiki.php.net/rfc/debugable-enums
> > * Implementation: https://github.com/php/php-src/pull/21425
>
> The RFC currently only mentions:
>
> > var_dump(Foo::Bar); // produces an array with "Bar is a case of the Foo
> enum"
>
> But it would be good for it to spell out the full output for the
> examples.
>

Done, examples now show the full output


> From the implementation, I can see:
>
> > object(Foo)#%d (1) {
> >  [0]=3D>
> >  string(14) "Foo::Bar =3D Baz"
> > }
>
> I think the enum(Foo::Bar) header should be preserved. If the user
> wants to print some ancillary data for some reason, I wouldn't object
> to that.
>

Done, the header is now preserved. I also removed the object handler
identifier, which I don't think is as needed with enums.

Based on my understanding of the RFC policy (
https://github.com/php/policies/blob/main/feature-proposals.rst), this
qualifies as a major change, so there is now a cooldown period of 14 days
before the earliest that a vote could start.

-Daniel

--000000000000dbe1b1064d13f053
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 15, 202=
6 at 11:01=E2=80=AFAM Ilija Tovilo &lt;<a href=3D"mailto:tovilo.ilija@gmail=
.com">tovilo.ilija@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">Hi Daniel<br>
<br>
On Fri, Mar 13, 2026 at 1:06=E2=80=AFAM Daniel Scherzer<br>
&lt;<a href=3D"mailto:daniel.e.scherzer@gmail.com" target=3D"_blank">daniel=
.e.scherzer@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I&#39;d like to start the discussion for a new RFC about removing the =
prohibition on __debugInfo() methods on enums.<br>
&gt;<br>
&gt; * RFC: <a href=3D"https://wiki.php.net/rfc/debugable-enums" rel=3D"nor=
eferrer" target=3D"_blank">https://wiki.php.net/rfc/debugable-enums</a><br>
&gt; * Implementation: <a href=3D"https://github.com/php/php-src/pull/21425=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/php/php-src/pull/=
21425</a><br>
<br>
The RFC currently only mentions:<br>
<br>
&gt; var_dump(Foo::Bar); // produces an array with &quot;Bar is a case of t=
he Foo enum&quot;<br>
<br>
But it would be good for it to spell out the full output for the<br>
examples.<br></blockquote><div><br></div><div>Done, examples now show the f=
ull output</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">From the implementation, I can see:<br>
<br>
&gt; object(Foo)#%d (1) {<br>
&gt;=C2=A0 [0]=3D&gt;<br>
&gt;=C2=A0 string(14) &quot;Foo::Bar =3D Baz&quot;<br>
&gt; }<br>
<br>
I think the enum(Foo::Bar) header should be preserved. If the user<br>
wants to print some ancillary data for some reason, I wouldn&#39;t object<b=
r>
to that.<br></blockquote><div><br></div><div>Done, the header is now preser=
ved. I also removed the object handler identifier, which I don&#39;t think =
is as needed with enums.</div><div><br></div><div>Based on my understanding=
 of the RFC policy (<a href=3D"https://github.com/php/policies/blob/main/fe=
ature-proposals.rst">https://github.com/php/policies/blob/main/feature-prop=
osals.rst</a>), this qualifies as a major change, so there is now a cooldow=
n period of 14 days before the earliest that a vote could start.</div><div>=
<br></div><div>-Daniel</div></div></div>

--000000000000dbe1b1064d13f053--