Den 2021-03-23 kl. 18:19, skrev Nikita Popov:
On Tue, Mar 23, 2021 at 5:01 PM Nicolas Grekas
<nicolas.grekas+...@gmail.com <mailto:nicolas.grekas%2b...@gmail.com>>
wrote:
Hello Nikita,
Picking up a loose thread:
https://wiki.php.net/rfc/custom_object_serialization
<https://wiki.php.net/rfc/custom_object_serialization>
introduced a
replacement for Serializable in PHP 7.4, so it's time to think
about
deprecating and removing the old mechanism:
https://wiki.php.net/rfc/phase_out_serializable
<https://wiki.php.net/rfc/phase_out_serializable>
This RFC follows a rather conversative approach. In PHP 8.1
there will be a
deprecation warning if Serializable is implemented without also
implementing __serialize() and __unserialize(). In PHP 9.0,
support for
Serializable is dropped internally, and only the interface
retained. In PHP
10.0 the interface is dropped as well.
Reading the comments in this thread, the three-step approach is
surprising to some.
What about deprecating in 8.1 and removing in 9.0 instead?
The stub Serializable interface can be provided in userland via a
polyfill, if anyone really needs a smoother transition plan.
I'd really like to see this deprecation in 8.1, to stop ppl from
writing new implementations of Serializable asap.
I've updated the RFC to follow this suggestion. Björn, please tell me
whether this addresses your concerns.
Regards,
Nikita
Yes it does, very good!
r//Björn L
