Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114606
MIME-Version: 1.0
In-Reply-To: <PA4PR02MB68005CAC217AD3B0EAB5DCE7B8259@PA4PR02MB6800.eurprd02.prod.outlook.com>
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>
Date: Wed, 26 May 2021 10:44:21 +0500
Message-ID: <CAC_PL4yzTOrq3HaSES928xoqN4_q9-EK1LJ3n8zUzzAQU4+0eA@mail.gmail.com>
To: =?UTF-8?Q?Iv=C3=A1n_Arias?= <txigreman@hotmail.com>
Cc: someniatko <someniatko@gmail.com>, Hendra Gunawan <the.liquid.metal@gmail.com>, 
	Karoly Negyesi <karoly@negyesi.net>, Marco Pivetta <ocramius@gmail.com>, Lynn <kjarli@gmail.com>, 
	"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: office.hamzaahmad@gmail.com (Hamza Ahmad)

Hello,
I read about this extension times ago but didn't know whether it had
been public. If Nikita is reading this, I request him to think of
proposing a modified version of this extension bundled with PHP.
In simple words, he can hide the function that registers a class that
serves as a prototype of a built-in type. And, also provide with
scalar methods for string, int, float and arrays. To get handler
registering functionality added to core, there should be a separate
RFC.
While I read this thread for the first time, I had following suggestions:
1. All array functions should be moved to its scaler object, and the
word "array_" should also be removed.
2. To maintain backward compatibility, all array_* functions will
become method aliases of scaler array.
3. ArrayObject will also exist for the compatibility purpose, and its
methods will also be added to the scaler array.
Thus, array() or [] will return scaler array object, and following
syntax would become valid:
`[1,2,3,4,5,6,7,8,9] -> reverse();`
`array(1 =3D> 'a', 2 =3D> 'b') -> flip();`
If it happens, users will automatically be stopped from passing
non-array values to array functions, and the error will be caught
earlier.
Regards

On 5/26/21, Iv=C3=A1n Arias <txigreman@hotmail.com> wrote:
> Hi all,
>
> It sounds like scalar objects by Nikita:
> https://github.com/<https://github.com/nikic/scalar_objects>nikic<https:/=
/github.com/nikic/scalar_objects>/scalar_objects<https://github.com/nikic/s=
calar_objects>
>
> Regards,
> Iv=C3=A1n Arias.
>
> Get Outlook for Android<https://aka.ms/AAb9ysg>
>
> ________________________________
> From: Hendra Gunawan <the.liquid.metal@gmail.com>
> Sent: Tuesday, May 25, 2021 10:58:46 PM
> To: someniatko <someniatko@gmail.com>
> Cc: Karoly Negyesi <karoly@negyesi.net>; Marco Pivetta <ocramius@gmail.co=
m>;
> Lynn <kjarli@gmail.com>; internals@lists.php.net <internals@lists.php.net=
>
> Subject: Re: [PHP-DEV] A little syntactic sugar on array_* function calls=
?
>
> Hello.
>
>>
>> ```php
>> $array|>map($fn1, ?)|>filter(?, $fn2);
>> $array->map($fn1)->filter($fn2);
>> ```
>>
>
> Whitespace removal is not a solution for code length problems.
> You might have a new problem if you do it. "|" is very similar
> to the lowercase "L" and uppercase "i".
>
> It's just an extra 3 characters (", ?" or "?, "). For most people,
> this is not a problem at all. people tend to write "one statement per lin=
e"
> rather than "multi statement line". I myself usually write no more than
> 3 statements per line if they are less than 120 characters.
>
> The real problem is there is no consistency for "haystack vs needle"
> position. There are RFCs to fix this (along with the naming convention
> problem), but none of them are successful.
>
>> The pipe operator feels like a poor solution while "->" would do
>> exactly what people want.
>
> Not so poor if we
> * use "~>" as pipe operator rather than "|>"
> * redesign the api under their proper namespace and strictly place
>   the "haystack" as the first function argument.
>
> Regards,
> Hendra Gunawan.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>