Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102799
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4Nr4TT+uh5od4UMGSp822TK4ShrH3EUV7W0JSBN-yLHXog@mail.gmail.com>
References: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
 <CAJd4=YYTP0caBhQda1HheiamHPtvO2XqXN4R=DgWF1iMdC7DeQ@mail.gmail.com>
 <CAJHtznybD1L5MnzhcNB_Kb0UPgag3zbrpOtr5zbfWCehx++R6w@mail.gmail.com>
 <8062036.rYxh8IFiYi@vulcan> <CAJHtznzG_VVzD2ZAZF_AcemJdq73mwPWBu7FLJMYqjgHW5Jh5A@mail.gmail.com>
 <CAFMT4Nr4TT+uh5od4UMGSp822TK4ShrH3EUV7W0JSBN-yLHXog@mail.gmail.com>
Date: Fri, 13 Jul 2018 11:20:11 +0100
Message-ID: <CALKiJKp6HB7hO4hBAF808pVPv+Lx9A5gXoST0dMk7MH-+migww@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000037fe890570ded340"
Subject: Re: [PHP-DEV] [RFC] Typed Properties
From: rowan.collins@gmail.com (Rowan Collins)

--00000000000037fe890570ded340
Content-Type: text/plain; charset="UTF-8"

On 11 July 2018 at 14:44, Levi Morrison <levim@php.net> wrote:

> > My logic is quite simple:
> > 1.  Something as big as Typed Properties shouldn't be a last minute,
> rushed
> > RFC.  Really - any RFC shouldn't - but in particular major language
> changes.
>
> I have seen this sentiment expressed elsewhere. I want to personally
> affirm that Nikita and Bob have been working hard on this for a long
> time. This is not a last minute change being rushed. They have been
> quite thorough and have discovered and fixed many edge cases that I
> suspect other authors would not have found or would have ignored. Yes,
> it is being voted on in the narrow gap between first alphas and
> feature freeze but that does not mean it is rushed.
>
>

They have indeed discovered many edge cases, and the RFC is extremely
thorough. But by the same token, they have made judgement calls about the
best way to handle some of those edge cases, and the RFC is 8000 words
long.

That's a lot of information for the rest of us to digest, and it's not just
trivia: accepting any implementation of this feature means making some
far-reaching decisions for the future typing functionality of the language.
For instance, I think the initialisation requirements for non-nullable
properties deserve a discussion in their own right, but I haven't yet had
time to write up my thoughts.

This isn't about rejecting the hard work that has gone into this; it's
about making sure there isn't some tweak we want to make before people
start building code that relies on it.


[Incidentally, I just noticed that we have both
https://wiki.php.net/rfc/typed-properties-v2 and
https://wiki.php.net/rfc/typed_properties_v2 - should this actually have
been "3.0"?]

Regards,
-- 
Rowan Collins
[IMSoP]

--00000000000037fe890570ded340--