Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108412
MIME-Version: 1.0
References: <D5ACEB01-4E1E-407A-8441-D8C6E0D36CCA@gmail.com>
In-Reply-To: <D5ACEB01-4E1E-407A-8441-D8C6E0D36CCA@gmail.com>
Date: Thu, 6 Feb 2020 13:05:51 +0100
Message-ID: <CAF+90c9yUeccgQqZmHv-aTEfm9vm8HQ72LrH0T736560AftR2A@mail.gmail.com>
To: Steven Wade <stevenwadejr@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001dd5fc059de71938"
Subject: Re: [PHP-DEV] [RFC - discussion] __toArray()
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000001dd5fc059de71938
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 4, 2020 at 2:03 PM Steven Wade <stevenwadejr@gmail.com> wrote:

> Hi all,
>
> I=E2=80=99d like to officially open my __toArray() RFC <
> https://wiki.php.net/rfc/to-array> up to discussion. I=E2=80=99ve delayed
> changing the status until I had more time to respond to the discussion, b=
ut
> since it=E2=80=99s been brought up again <https://externals.io/message/10=
8351>, I
> figured now is the best time.
>
> https://wiki.php.net/rfc/to-array <https://wiki.php.net/rfc/to-array>


One of the things that stand out to me in this RFC is that once you set
strict_types=3D1 (which surely we all do :P), not a lot is left of it. Whil=
e
there are quite a few places where objects can be implicitly converted to
strings (say echo, concatenation, etc), there are not a lot of places where
objects can be implicitly converted to array. A quick grep has around 500
string conversions in the codebase, and 20 array conversions.

Nikita

--0000000000001dd5fc059de71938--