Re: Proposal for a RFC
| From: | Kalle Sommer Nielsen | Date: | Sat, 04 May 2019 16:08:15 +0000 |
| Subject: | Re: Proposal for a RFC | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-105591@lists.php.net to get a copy of this message | ||
Hi
Den lør. 4. maj 2019 kl. 17.58 skrev Steven Wade <stevenwadejr@gmail.com>:
>
> 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 developer to
> specifiy how a class is cast to an array. The idea is the same mentality 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
--
regards,
Kalle Sommer Nielsen
kalle@php.net