Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102895
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BL0PR02MB443503A3D9340A7A91E8AD5DAC5D0@BL0PR02MB4435.namprd02.prod.outlook.com>
References: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
 <CAF+90c8ZG8FYy74i+HmGPb=YgsaT=CLRDqs0TxNo+X13AeyeTg@mail.gmail.com> <BL0PR02MB443503A3D9340A7A91E8AD5DAC5D0@BL0PR02MB4435.namprd02.prod.outlook.com>
Date: Tue, 17 Jul 2018 20:02:05 +0200
Message-ID: <CAF+90c9o3ou_QGGMAV=S6NeXeTB+-ew=um=+ZJocQWDhgvHDNw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000076f041057135beaf"
Subject: Re: [PHP-DEV] Re: [RFC] Typed Properties
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000076f041057135beaf
Content-Type: text/plain; charset="UTF-8"

On Tue, Jul 17, 2018 at 12:10 AM, Zeev Suraski <zeev@zend.com> wrote:

> > Based on the feedback we received, we have decided to target PHP 7.4 for
> this
> > RFC. A main factor for this decision was that the RFC requires some
> non-trivial
> > changes to 3rd-party extensions for full compatibility. This would put
> the
> > ongoing (but nearly complete) effort to port extensions to PHP 7.3 back
> to
> > square one.
>
> As I mentioned beforehand, I think it's good it wasn't rushed into 7.3 and
> at the same time sorry it's not being targeted for 8.0.
>
> > Now that the target version is decided and the last open questions in
> the RFC
> > have been resolved, we plan to open voting tomorrow.
>
> IMHO one of the key reasons for not putting it into 7.3 was the fact that
> very little discussion about the actual proposal actually happened because
> it arrived so late in the 7.3 release cycle.  Most of the discussion under
> the Typed Properties thread actually had to do with whether or not it
> should go into 7.3, 7.4 or 8.0 - and not about the specifics of the
> proposal.  I skimmed through the thread and found just a handful of
> responses that dealt with the specific of the proposals - most of them
> unanswered (unless I'm missing some internals email somehow).
>
> With this in mind, I think that now that the meta parts are finalized, we
> should allow a bit more time for real meaningful discussion about the
> proposal to happen.  I understand that you don't want to delay this to a
> later time in the 7.4 process, but delaying it by a week or so will allow
> people to actually review the proposal in more detail without the
> uncertainty that surrounded it beforehand - and perhaps have their concerns
> addressed.  Given that 7.4's finalization date is a year away, and there
> are no conflicting RFCs in the queue - a week will not have any sort of
> negative influence on the proposal, but might have some positive impact on
> its contents.
>
> Zeev
>

Sure, we can wait another week. Unless the additional discussion results in
major changes to the RFC, we'll start voting next Monday (2018-07-23). In
the interest of avoiding further delays, please try to view this as a hard
deadline: If you would like to discuss some aspect of the proposal or raise
a concern, please do so now rather than on Monday morning.

Nikita

--00000000000076f041057135beaf--