Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121977
Date: Sat, 09 Dec 2023 17:15:55 +0000
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CAGgaK7+w_zdp30Pi5nJ-y+GPEkfc2xHfFUW+DwdpNtY8iPjMHg@mail.gmail.com>
References: <CAGgaK7+w_zdp30Pi5nJ-y+GPEkfc2xHfFUW+DwdpNtY8iPjMHg@mail.gmail.com>
Message-ID: <54BE3A8E-046E-495E-B371-CCF917B6BB49@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC][Discussion] NotSerializable attribute
From: rowan.collins@gmail.com (Rowan Tommins)

On 9 December 2023 12:30:29 GMT, Max Semenik <maxsem=2Ewiki@gmail=2Ecom> wr=
ote:
>Hi, I'd like to propose a new attribute, #[NotSerializable]=2E This
>functionality is already available for internal classes - userspace shoul=
d
>benefit from it, too=2E

If this ends up approximately the same as implementing serialisation as an=
 exception, it feels quite a thin feature=2E If you put __sleep and __wakeu=
p as shown into a trait, it's already as short and explicit as "use NotSeri=
alizable;"

What would make it more compelling is if the engine itself could do more w=
ith the attribute=2E For instance, a direct isSerializable() on ReflectionC=
lass that covered both internal and attribute-marked classes=2E

It would also be useful to have some interface for classes that are *somet=
imes* serializable, because they contain open-ended collections of other ob=
jects=2E An example being exceptions, which may collect objects as part of =
the backtrace information=2E Such a class could iterate its contained objec=
ts, checking if they are unserializable classes, or classes which should re=
cursively be asked if the instance is serializable=2E

Regards,

--=20
Rowan Tommins
[IMSoP]