Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92470
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <57164CE8.4090307@garfieldtech.com>
References: <CAL=_i_mzF5U4kb487igLrMPvnK5UUNP0W1FA+MYHWMjmypJ3Cg@mail.gmail.com>
 <BY2PR0201MB1784951F449DA564BF12AE3DBF6C0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAL=_i_mxPnzm4O7mpVFiGTtxnwDSUtpzM7f8Su=LwkHTa_agOw@mail.gmail.com>
 <CAL=_i_nJrbCaN4RC0HrV8t4a07ugwG-j373wocaidNfJtWAKNA@mail.gmail.com>
 <5716310B.4060104@zend.com> <CAL=_i_mriQQ_MKEw-zm_xfJh5tYb6_nzE6iLMXh0zYEuWG_OiQ@mail.gmail.com>
 <57163CB0.70608@zend.com> <5716410C.1080904@gmail.com> <57164550.7070008@zend.com>
 <57164889.1080609@gmail.com> <57164CE8.4090307@garfieldtech.com>
Date: Tue, 19 Apr 2016 11:30:38 -0400
Message-ID: <CAOsHV+sRN_ew_c+f+V7XyvYTvC_Z_agqHNwNJuqwhjCsjELWeg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113dc36ef16fa20530d82916
Subject: Re: [PHP-DEV] RFC: Functional Interfaces
From: marcio.web2@gmail.com (Marcio Almada)

--001a113dc36ef16fa20530d82916
Content-Type: text/plain; charset=UTF-8

Hi!

2016-04-19 11:21 GMT-04:00 Larry Garfield <larry@garfieldtech.com>:

> On 4/19/16 10:02 AM, Rowan Collins wrote:
>
>> Dmitry Stogov wrote on 19/04/2016 15:48:
>>
>>> callable-type is much simpler solution for this use-case.
>>> Usage of Interfaces to check function prototypes is a bit tricky, but
>>> yes, this is a possible use-case.
>>> Do you like to work with framework, that use this trick for every
>>> callback?
>>>
>>
>> If you don't use __invoke as the function name, you can have a single
>> class implement multiple contracts, e.g. to register for more than one
>> event type with different signatures.
>>
>> I guess if you had callable-types *and* union types, you could get the
>> best of both worlds:
>>
>> interface UserEventCallbackInterface {
>>     public function handleUserEvent(UserEvent $event): boolean;
>> }
>> public function registerCallback(EventCallbackInterface|callable(Event):
>> boolean $handler) { ... }
>>
>> The implementation has to be a bit fiddlier here, because you need to
>> sometimes call $handler->handleUserEvent($event) and sometimes
>> $handler($event); with a functional interface, the engine makes
>> $handler->handleUserEvent($event) work for you. The cost is that the call
>> site has to be a bit more verbose to specify the interface, rather than
>> implicitly meeting the contract.
>>
>>
I believe Joe has both $handler->handleUserEvent($event) and
$handler($event) cases covered already. This means that
$handler->handleUserEvent($event), $handler() and $handler->__invoke($event)
should be 100% equivalent.


> Regards,
>>
>
> Which is why I'm not sure I like that approach, because the place I then
> call $handler needs to have a conditional in it.  There's another RFC that
> was posted to Twitter but hasn't made it to the list yet that seems to
> solve this better:
>
> https://wiki.php.net/rfc/callable-types
>
> (My apologies to the authors if they aren't done with it; it's on the wiki
> so I'm assuming it's safe to mention in public.)
>
>
Yes, it it's ok to mention the RFC. We are going to move it to discussion
phase ASAP some minor issues get a fix :)


> That allows just the callable-type syntax (which I presume is what you're
> referencing), but you can then pass an object in using []-callable syntax:
> [$handler. 'handleUserEvent'], and then registerCallback() doesn't care if
> it was a function, method, closure, or whatever else. It can just () it.
>
> --
> --Larry Garfield
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a113dc36ef16fa20530d82916--