Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102867
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
References: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
Date: Mon, 16 Jul 2018 21:45:14 +0200
Message-ID: <CAF+90c8ZG8FYy74i+HmGPb=YgsaT=CLRDqs0TxNo+X13AeyeTg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000086843b057123116e"
Subject: Re: [RFC] Typed Properties
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000086843b057123116e
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 20, 2018 at 11:59 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> Bob and I would like to present a new typed properties proposal for your
> consideration:
>
>     https://wiki.php.net/rfc/typed_properties_v2
>
> The proposal allows you to annotate properties with types, which are
> enforced at runtime. Unlike the previous RFC on this topic, the new
> proposal also supports typed static properties and references to typed
> properties.
>
> Please note that next to the main body, the RFC also contains an
> "Alternatives" section, which explores the problem space and considers
> trade-offs of different behaviors in some detail.
>
> Finally, while this RFC currently targets PHP 7.3, this is a large and
> complex proposal and we may not be able to meet the deadline, in which case
> this feature will go into the next PHP version.
>
> Regards,
> Nikita
>

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.

Now that the target version is decided and the last open questions in the
RFC have been resolved, we plan to open voting tomorrow.

Regards,
Nikita

PS: Thanks goes to the RMs for delaying the release schedule and providing
us with the opportunity to target PHP 7.3, even if we did not end up using
it.

--00000000000086843b057123116e--