Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92893
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 207.46.100.112 as permitted sender)
To: Levi Morrison <levim@php.net>, Joe Watkins <pthreads@pthreads.org>
CC: internals <internals@lists.php.net>, Tom Worster <fsb@thefsb.org>
Thread-Topic: [PHP-DEV] Re: Request to withdraw RFC's for nullable types for
 only return values
Thread-Index: AQHRoWRe782dRDYm1kuNWD0UZVTnlZ+fm7+pgAALLYCAAAAymoAAAjiAgAACLoCAAA56AIAAAHIi
Date: Thu, 28 Apr 2016 18:54:16 +0000
Message-ID: <BY2PR0201MB17847220E76760C84BB5AACBBF650@BY2PR0201MB1784.namprd02.prod.outlook.com>
References: <CAFMT4NpBi80uJ-_-==4Wd5h87k=fq3h7N9ygph1kCHg9Czc_Kw@mail.gmail.com>
	<BY2PR0201MB17848D27325287FFD9785771BF650@BY2PR0201MB1784.namprd02.prod.outlook.com>
	<CAFMT4Nr+m4LVQC81+quTwzhu1tSzLq=Zd_fvJwpo_HfnNshSKQ@mail.gmail.com>
	<BY2PR0201MB178472C732BF8DEE68D8D940BF650@BY2PR0201MB1784.namprd02.prod.outlook.com>
	<CAFMT4Nrj4c+y+j7tMr42NoMTNq_9Xf9jGNo2jLFUy153K=ks7g@mail.gmail.com>
	<CAL=_i_kPW8yiynJ=Qksjz_BCZ1FCwck28_+rCk1Jn94qUDh+fg@mail.gmail.com>,<CAFMT4No4atnAQ4oRYXLKLb4JGMBG=HMhWOi6JXs=K0HbKsANEg@mail.gmail.com>
In-Reply-To: <CAFMT4No4atnAQ4oRYXLKLb4JGMBG=HMhWOi6JXs=K0HbKsANEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2016 18:54:16.7416
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1781
Subject: Re: [PHP-DEV] Re: Request to withdraw RFC's for nullable types for
 only return values
From: dmitry@zend.com (Dmitry Stogov)

Levi, I don't understand, why do you keep trying to own "Nullable Types" RF=
C, if you like completely different "Union Types".

________________________________________
From: morrison.levi@gmail.com <morrison.levi@gmail.com> on behalf of Levi M=
orrison <levim@php.net>
Sent: Thursday, April 28, 2016 9:47:18 PM
To: Joe Watkins
Cc: Dmitry Stogov; internals; Tom Worster
Subject: Re: [PHP-DEV] Re: Request to withdraw RFC's for nullable types for=
 only return values

On Thu, Apr 28, 2016 at 11:55 AM, Joe Watkins <pthreads@pthreads.org> wrote=
:
> Levi,
>
>     Why do you need to block Dmitry's return type nullable RFC ?
>
>     We need to move forward, that has an implementation, ready for a long
> time, doesn't seem to block nullable parameter types rfc, either separate=
ly
> or as part of unions.
>
>     So, I'm not understanding why you need to hold up Dmitry any more.
>
>     Please, explain.
>
> Cheers
> Joe
>
> On Thu, Apr 28, 2016 at 6:47 PM, Levi Morrison <levim@php.net> wrote:
>>
>> On Thu, Apr 28, 2016 at 11:43 AM, Dmitry Stogov <dmitry@zend.com> wrote:
>> > your Nullable RFC doesn't propose working implementation.
>> >
>> > ________________________________________
>> > From: morrison.levi@gmail.com <morrison.levi@gmail.com> on behalf of
>> > Levi Morrison <levim@php.net>
>> > Sent: Thursday, April 28, 2016 8:39:03 PM
>> > To: Dmitry Stogov
>> > Cc: internals; Tom Worster
>> > Subject: Re: Request to withdraw RFC's for nullable types for only
>> > return values
>> >
>> > On Thu, Apr 28, 2016 at 11:07 AM, Dmitry Stogov <dmitry@zend.com> wrot=
e:
>> >> Thanks for catching the BC break.
>> >> Fortunately, we didn't release 7.0.6 with this problem.
>> >>
>> >> I see some sense in introducing that check, but changing behaviour
>> >> requires RFC and definitely not allowed in minor versions.
>> >>
>> >> I'm not going to withdraw
>> >> https://wiki.php.net/rfc/nullable_return_types
>> >> It doesn't prohibit usage of nullable for arguments, and even sets
>> >> additional question.
>> >
>> > In that case: are you fine with my RFCs going to vote first (and
>> > soon)? We presently have four somewhat competing RFCs and need to work
>> > out voting order.
>> >
>> > Tom: are you willing to withdraw or wait for my RFCs to vote first?
>>
>> It doesn't have an implementation, sure. But you already worked out
>> return types, the basics are already there in parameter types and
>> there's an implementation in HHVM. Do you really think this would be a
>> blocker? There is no reason to believe that a short-hand nullable
>> types implementation cannot be reasonably done.
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>

Let me firstly say I'm not trying to "block" Dmitry's RFC as some sort
of political campaign. Let me try to straighten this:

As evidenced by this bug report that needs a fix there is a need for
nullable parameter types that is not tied to a default of null.
Dmitry's RFC does not handle this. Nor does Tom's.

There is an RFC that can solve both return types and parameter types.
I'm asking them to withdraw because they don't meet those needs and
there is an RFC that does. It just so happens to be mine. It also
happens to be the first drafted RFC.

This is not an unreasonable request. In fact, it's the much nicer
option that just opening vote on mine first without talking about it
on list at all. And lastly, it's just a request. They don't have to
withdraw.