Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114825
MIME-Version: 1.0
References: <CAGBsUrfnW-rEb6iy2_b5xumw_f-Ny-9vySqPFnfqtRiEaSXY+Q@mail.gmail.com>
In-Reply-To: <CAGBsUrfnW-rEb6iy2_b5xumw_f-Ny-9vySqPFnfqtRiEaSXY+Q@mail.gmail.com>
Date: Fri, 11 Jun 2021 09:58:17 +0300
Message-ID: <CAPVMwwuP7Km6OX0EqmE3GkMzK3g=f_Sv6-M2e6wivMZJCnFPZw@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f0649205c47808ef"
Subject: Re: [PHP-DEV] [VOTE] Deprecate autovivification on false
From: dmitrystogov@gmail.com (Dmitry Stogov)

--000000000000f0649205c47808ef
Content-Type: text/plain; charset="UTF-8"

hi,

I wouldn't care about disabling autovivification on false, but I vote "No",
because I'm against the deprecation.

Thanks. Dmitry.

On Wed, Jun 9, 2021 at 11:24 PM Kamil Tekiela <tekiela246@gmail.com> wrote:

> Hi Internals,
>
> I have limited the RFC to disabling autovivification on false only, which
> was the initial scope of the RFC. The only two possible cases remaining
> will be undefined and null. After what Tyson Andre clearly explained, null
> is commonly used and leads to many more complex situations.
>
> I have opened voting on https://wiki.php.net/rfc/autovivification_false
> which will end on 2021-06-23T20:00:00Z
>
> Link to the discussion thread: https://externals.io/message/114595
>
> The implementation is pending, but if someone wants to suggest one, please
> feel free.
>
> Regards,
> Kamil
>

--000000000000f0649205c47808ef--