Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105591
MIME-Version: 1.0
References: <FB70FDD7-53AA-4DB4-B747-6E109BE52C2E@gmail.com>
In-Reply-To: <FB70FDD7-53AA-4DB4-B747-6E109BE52C2E@gmail.com>
Date: Sat, 4 May 2019 19:08:15 +0300
Message-ID: <CAJW__o1uANrBOKrQD6X0YJKDwCEi=eMd9gUL36vxe=GvxH1__Q@mail.gmail.com>
To: Steven Wade <stevenwadejr@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Proposal for a RFC
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

Den l=C3=B8r. 4. maj 2019 kl. 17.58 skrev Steven Wade <stevenwadejr@gmail.c=
om>:
>
> Hi Internals team!
>
> I have an idea for a feature that I'd love to see in the language one day=
 and wanted to run the idea by you all.
>
> The idea is to add a new magic method "__toArray()" that would allow a de=
veloper to specifiy how a class is cast to an array. The idea is the same m=
entality of __toString(), but, for arrays.

While this sounds great and all, I do wonder about the implications it
may have on the already existing behavior of type casting an object
into an array which returns current public/protected/private property
values. While this functionality is not an ideal or by design, it is
fairly heavily (ab-)used, meaning that it is a potential BC break
without the ability to an alternative.

See this example: https://3v4l.org/ONMoi

--=20
regards,

Kalle Sommer Nielsen
kalle@php.net