Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114661
MIME-Version: 1.0
References: <CAOfzkkxbS6CQidg4-uai42PPRPHfWWL9UZTd+zDgspXsFSr5zg@mail.gmail.com>
 <CABAhh3ER9_Pv6g7jANQ-qoTE6DmTLHWTv6Ggjr+qvnbXqXBB0w@mail.gmail.com>
 <CANS-=pc0qe7aRLAPxSjj+AT46m8Y=ARB4L8AwESKmiQVK=dEJw@mail.gmail.com>
 <CABAhh3GfC+69FoGzUQxC+O3MhiETgN_s4edYQL2FUndrex5-JA@mail.gmail.com>
 <CAOfzkkxSw7euY_nhOVo+gHx8FXjycVey84j+YiEZMXpPAkvKmA@mail.gmail.com>
 <CABAhh3GwwmsyyFwbwN6OHFKCT1zkTdBmmKcCvSC=WxxAwyDh+A@mail.gmail.com>
 <CAG4FTXySSCV8io6kkgExAewj+DG2eGfm2r=Vg9Vr6t+M2xQx2A@mail.gmail.com>
 <PA4PR02MB68005CAC217AD3B0EAB5DCE7B8259@PA4PR02MB6800.eurprd02.prod.outlook.com>
 <E5A7BE78-D8E2-45AF-B2B4-40538DFEA57F@newclarity.net> <CAG4FTXyz-EkWPTbaBXaKLSFmaaidpLokuuzsg_FbMK0YwDEPEA@mail.gmail.com>
 <CD1CCD71-B0DE-48A5-A18F-E23E90B083F7@newclarity.net> <CAF+90c8RhWxKzUKfC4o29gC-nibf33m2qf+Nu4=zTRamLG6W8Q@mail.gmail.com>
In-Reply-To: <CAF+90c8RhWxKzUKfC4o29gC-nibf33m2qf+Nu4=zTRamLG6W8Q@mail.gmail.com>
Date: Sat, 29 May 2021 05:11:39 +0700
Message-ID: <CAG4FTXxnZ7nJUCatPGyTyF9dh=Zrky9ejWn52DpDJ96+ifX0VQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Mike Schinkel <mike@newclarity.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] A little syntactic sugar on array_* function calls?
From: the.liquid.metal@gmail.com (Hendra Gunawan)

Hello.

>
> The only correct way to resolve this issue is to not support mutable oper=
ations.
>

Correct me if I'm wrong: scalar object will hit memory limit earlier
than old API if it applied to $some_huge_shared_array for several
method calls.

>
> I don't think there's much need for mutable operations. sort() and shuffl=
e() would be best implemented by returning a new array instead. array_push(=
) is redundant with $array[]. array_shift() and array_unshift() should neve=
r be used. array_pop() and array_splice() are the only sensible mutable arr=
ay methods that come to mind, and I daresay we can do without them.
>

Suppose that we all agree with that. **Will scalar object preserve
most of all functionality of the old API?** Some functions are very
handy that keep us away from the gory detail implementation. In array
case, we know that PHP array is a combination of array and plain
object in JS term. There is a trend in user land PHP library that they
are just copying the JS array API and poorly preserving the existing
functionality of PHP old API. Implicitly, the author of this thread
wants this to happen.

If I am not wrong, scalar object date back to before PHP 7.0. Is there
any consideration why scalar object was not escalated to the next
phase, say to RFC?

Regards
Hendra Gunawan.