Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104854
MIME-Version: 1.0
References: <CAF+90c_=u2NxcWA7tRYnr3RnYJfShNus4WYHTDmcqzAVHcWcoQ@mail.gmail.com>
In-Reply-To: <CAF+90c_=u2NxcWA7tRYnr3RnYJfShNus4WYHTDmcqzAVHcWcoQ@mail.gmail.com>
Date: Thu, 21 Mar 2019 15:20:32 +0100
Message-ID: <CAF+90c9bFF0jvwZMTqtVXnSgg8-nhFtEROKhEzRKsNcG1nw2Tw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e65d3f05849b71eb"
Subject: Re: [VOTE] New custom object serialization mechanism
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000e65d3f05849b71eb
Content-Type: text/plain; charset="UTF-8"

On Fri, Mar 1, 2019 at 4:08 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I have opened voting on
> https://wiki.php.net/rfc/custom_object_serialization. The vote will be
> open until 2019-03-15.
>
> You can find the discussion thread for this proposal here:
> https://externals.io/message/103823
>
> Regards,
> Nikita
>

Vote closed a bit late here ... the RFC is accepted with 20 votes in favor
and 7 against.

Regarding deprecation, I think I will target this at PHP 8. The new
mechanism will be there for the people who are running into the limits of
the existing one, but we probably don't need everybody to switch over right
this minute just yet.

Regards,
Nikita

--000000000000e65d3f05849b71eb--