Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113724
MIME-Version: 1.0
References: <CAF+90c_8Z389ZA2725QDT0bx8sTfaeh4jXRs02E6GZy83pXkVg@mail.gmail.com>
In-Reply-To: <CAF+90c_8Z389ZA2725QDT0bx8sTfaeh4jXRs02E6GZy83pXkVg@mail.gmail.com>
Date: Tue, 23 Mar 2021 17:01:40 +0100
Message-ID: <CAOWwgpkWMy6VyEPXTsuLUsmSTY1tmmCTqg3HmB6r_uBzFEv=Lg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f6930005be364cba"
Subject: Re: [PHP-DEV] [RFC] Phasing out Serializable
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000f6930005be364cba
Content-Type: text/plain; charset="UTF-8"

Hello Nikita,


Picking up a loose thread:
> 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
>
> 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.

Nicolas

--000000000000f6930005be364cba--