Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119415
MIME-Version: 1.0
References: <8f530a4a-bf48-4259-877e-16ebf8082936@app.fastmail.com>
 <CA+kxMuQWYqE-LMuQPU66xK1DAZNOdV_-A677oSKyPzhJeEZFpQ@mail.gmail.com>
 <9c97b0b1-e17e-4eec-8cf5-fad86aca2da6@app.fastmail.com> <CA+kxMuRTFvMwCnYbs_CWszESULRENKu-ndK3U+b5tMX96HmJ=w@mail.gmail.com>
 <f9df091f-15c0-4469-b657-b96e4321e763@app.fastmail.com> <CA+kxMuRjZBQ4cutXSbLy2fohuux45apAyEYFwCMs8_T40E_7yw@mail.gmail.com>
 <87c1e01f-0ef0-4096-996c-030be1fab73f@app.fastmail.com>
In-Reply-To: <87c1e01f-0ef0-4096-996c-030be1fab73f@app.fastmail.com>
Date: Tue, 24 Jan 2023 12:36:27 +0100
Message-ID: <CAPzBOBMz_yEY8iBh7n+C8U0fngBQFfT1w9QQCpAXp9meeKKJyg@mail.gmail.com>
To: Ollie Read <php@ollie.codes>
Cc: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Introduce the abiltiy to use the first-call-callable
 syntax on non-static methods, statically
From: landers.robert@gmail.com (Robert Landers)

On Tue, Jan 24, 2023 at 12:06 PM Ollie Read <php@ollie.codes> wrote:
>
> You're absolutely correct, the problem I was trying to solve was the ability to reference a method without throwing around magic strings, apologies if that wasn't clear.
>
> The whole idea, or rather, need/want for it came about because of time spent with Javas functional side, though I understand that's safer to do because of the way Java handles type safety.
>
> The ::class pseudo type is great for providing a classes FQN, and class-string is great for ensuring values are valid class strings when using static analysis, but we don't have anything for methods, outside of IDE completion.
>
> The solution wouldn't even need to generate a closure, TBH, it would generate something that could then be used in the same manner.
>
> Using the current features of PHP, I'd probably imagine something that does just about the same as this:
>
> $method = new ReflectionMethod(MyClass::class, 'method');
>
> $collection->filter($method);
>
> Where the filter method does:
>
> foreach ($items as $item) {
>     if ($method->invoke($item)) {
>         //
>     }
> }
>
> Although reflection doesn't have the overhead that everyone thinks it does, this is a less than ideal solution, but I think it accurately portrays what I'm looking for.
>
> ---
> Best Regards,
> *Ollie Read*

> The ::class pseudo type is great for providing a classes FQN, and class-string is great for ensuring values are valid class strings when using static analysis, but we don't have anything for methods, outside of IDE completion.
>
> The solution wouldn't even need to generate a closure, TBH, it would generate something that could then be used in the same manner.

In C#, they have the `nameof()` operator that returns the name of the
symbol passed. So you still end up with a string, but the symbol can
easily be refactored.

https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/operators/nameof

Maybe something like this could help address the problem?

Robert Landers
Software Engineer
Utrecht NL