Re: Request to withdraw RFC's for nullable types for only return values
| From: | Dmitry Stogov | Date: | Thu, 28 Apr 2016 17:43:10 +0000 |
| Subject: | Re: Request to withdraw RFC's for nullable types for only return values | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-92881@lists.php.net to get a copy of this message | ||
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> wrote:
> 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?