Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118416
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-811-gb808317eab-fm-20220801.001-gb808317e
Mime-Version: 1.0
Message-ID: <d909da65-9702-4995-9e2e-a4bb6b627ebd@www.fastmail.com>
In-Reply-To: <01D4987C-FD37-4BD2-A1AC-DD10F808F248@gmail.com>
References: 
 <CABigaAWAMfjTh9FBhu-SQRfu9_pgqt5pp7uj4kmNg0QmXbnS-Q@mail.gmail.com>
 <62f48769.250a0220.37387.53b5SMTPIN_ADDED_MISSING@mx.google.com>
 <01D4987C-FD37-4BD2-A1AC-DD10F808F248@gmail.com>
Date: Thu, 11 Aug 2022 13:42:30 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [Concept] Extension methods
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, Aug 11, 2022, at 4:03 AM, Alex Wells wrote:

> Besides, I believe working with existing functions is more of a proble=
m=20
> than a bonus - because of the naming. You=E2=80=99d have to clutter yo=
ur code=20
> with `array_map` calls, even though it could easily be shortened to=20
> `map`.

A couple of trivial higher order functions and you're good to go.  I hav=
e a sampling of them here: https://github.com/Crell/fp/blob/master/src/a=
rray.php

(Modulo PHP's inconsistency between internal/user-space functions that f=
orce having separate functions for keyed and unkeyed arrays; any solutio=
n is going to have to deal with that problem.)

>> On 11 Aug 2022, at 07:36, Paul Crovella <paul.crovella@gmail.com> wro=
te:
>>=20
>> This is essentially making `->` the pipe operator with extra steps (`=
extension`/`use extension`) and less utility (not working on existing fu=
nctions.)
>
> Well, pipe operator is another option, but it=E2=80=99s got it=E2=80=99=
s downsides=20
> compared to extension methods:
>  - it's less versatile: extension methods are required to specify a=20
> type they=E2=80=99re extending, meaning they are methods, not function=
s. Hence,=20
> two different `map` method extensions can be imported in a single file=20
> (given they=E2=80=99re for different types - say one for `Collection`,=
 the=20
> other for `array`), unlike regular functions. I believe it=E2=80=99s c=
ommon=20
> place to use both `Collection::map` and `array::map` in a single file,=20
> but that wouldn=E2=80=99t be possible or would require aliasing
>  - it=E2=80=99s uglier: since it just uses functions, to avoid clashes=
 between=20
> same method names, prefixes would be required

Flipside: Pipe works on arrays and strings, which this would not.  And a=
rrays and strings are among the most common things to be chained in this=
 way.  (Most Collection objects are just alternate OOPy syntax around ar=
ray_map and array_filter, at the end of the day.)  Pipe also doesn't giv=
e the impression that the method is "part of" the object (it's not), whe=
reas extensions do, despite being effectively just an alternate syntax f=
or a public function that takes the object as an argument.

And functions can be easily namespaced.

--Larry Garfield