Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129024
Precedence: list
MIME-Version: 1.0
References: <CAPqq82sqFy1y77XLu8Kbncg18WNopeJdPrfB+JQ8FWNZ4XpTQg@mail.gmail.com>
 <CAPyj-LBG0nR75AUMXT0XCnpNnPP=T62NYvRQ34yeZpd+i=cTPw@mail.gmail.com>
 <CAPqq82sy1O9-J4yhvcPvsob3Rjdi1wFDW_t597850sBTbKc=sg@mail.gmail.com>
 <4b6abc36d8ab6cd306e95141869db3b0@bastelstu.be> <CAPqq82u7xhMDqmwuhEPOGqHdnrM3S2OM+HG=XpG-SyKPS3LofA@mail.gmail.com>
 <21ff8dee5016a1b7ecc412c44233abd1@bastelstu.be> <CAPqq82vPdraqE1DuJQ6w4pWpwr1koTHcj_o0pKV1dXxRoaguqg@mail.gmail.com>
 <3a20b5ef66fc23de6bad022685b41190@bastelstu.be>
In-Reply-To: <3a20b5ef66fc23de6bad022685b41190@bastelstu.be>
Reply-To: erictnorris@gmail.com
Date: Fri, 31 Oct 2025 08:16:47 -0400
Message-ID: <CA+NMNO0ULGv8M-YamTG6LK2f4AVNCHmt6TsPjng-3pSmncnyOg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC][Discussion] Add #[NoSerialize] attribute for
 excluding properties or classes from serialization
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: Dmytro Kulyk <lnkvisitor.ts@gmail.com>, Ilija Tovilo <tovilo.ilija@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000071644106427357f7"
From: eric.t.norris@gmail.com (Eric Norris)

--00000000000071644106427357f7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 31, 2025, 4:47=E2=80=AFAM Tim D=C3=BCsterhus <tim@bastelstu.be>=
 wrote:

> Hi
>
> Am 2025-10-30 23:24, schrieb Dmytro Kulyk:
> > If we go in that direction, I=E2=80=99d suggest keeping the name
> > #[NoSerialize], because it=E2=80=99s more general and clearly describes=
 the
> > action rather than the failure mode.
> > #[NotSerializable] reads more like an error state, while
> > #[NoSerialize] works naturally for both contexts =E2=80=94 skipping pro=
perties
> > silently and preventing class serialization (by throwing).
> >
> > This way, the attribute name remains short and declarative, while the
> > actual behavior (throwing vs skipping) can be determined by where it=E2=
=80=99s
> > applied =E2=80=94 on a class or on a property =E2=80=94 without introdu=
cing another
> > attribute.
>
> That makes sense to me and I don't have a suggestion for a better name.
>

I hope I'm not starting a bikeshed discussion, but I've been following
along - can I suggest "DoNotSerialize"? "NoSerialize" sounds odd to me,
whereas "DoNotSerialize" can be seen as both an instruction to PHP - "don't
serialize this property when serializing the class" - and an instruction to
developers - "do not attempt to serialize this class".

>

--00000000000071644106427357f7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_quote gmail_quote_container"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 31, 2025, 4:47=E2=80=AFAM Ti=
m D=C3=BCsterhus &lt;<a href=3D"mailto:tim@bastelstu.be">tim@bastelstu.be</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
Am 2025-10-30 23:24, schrieb Dmytro Kulyk:<br>
&gt; If we go in that direction, I=E2=80=99d suggest keeping the name<br>
&gt; #[NoSerialize], because it=E2=80=99s more general and clearly describe=
s the<br>
&gt; action rather than the failure mode.<br>
&gt; #[NotSerializable] reads more like an error state, while<br>
&gt; #[NoSerialize] works naturally for both contexts =E2=80=94 skipping pr=
operties<br>
&gt; silently and preventing class serialization (by throwing).<br>
&gt; <br>
&gt; This way, the attribute name remains short and declarative, while the<=
br>
&gt; actual behavior (throwing vs skipping) can be determined by where it=
=E2=80=99s<br>
&gt; applied =E2=80=94 on a class or on a property =E2=80=94 without introd=
ucing another<br>
&gt; attribute.<br>
<br>
That makes sense to me and I don&#39;t have a suggestion for a better name.=
<br></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
I hope I&#39;m not starting a bikeshed discussion, but I&#39;ve been follow=
ing along - can I suggest &quot;DoNotSerialize&quot;? &quot;NoSerialize&quo=
t; sounds odd to me, whereas &quot;DoNotSerialize&quot; can be seen as both=
 an instruction to PHP - &quot;don&#39;t serialize this property when seria=
lizing the class&quot; - and an instruction to developers - &quot;do not at=
tempt to serialize this class&quot;.</div><div dir=3D"auto"><div class=3D"g=
mail_quote gmail_quote_container"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--00000000000071644106427357f7--