Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92633
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 74.125.82.53 as permitted sender)
To: internals@lists.php.net
References: <CAOsHV+vDNGNThMDZU7_ZkTr2janDVmbjmNkuSGSc=3opLcPE-g@mail.gmail.com>
Message-ID: <5719EA39.2070408@seld.be>
Date: Fri, 22 Apr 2016 10:09:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAOsHV+vDNGNThMDZU7_ZkTr2janDVmbjmNkuSGSc=3opLcPE-g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV][RFC] Callable Types
From: j.boggiano@seld.be (Jordi Boggiano)

On 22/04/2016 05:12, Marcio Almada wrote:
> Hello everyone,
>
> We just completed the draft for the "Callable Types" RFC. This RFC has been
> recently mentioned during other type related threads on this mailing list,
> so it feels to be the right time to put the proposal in context:
>
> The proposal is at https://wiki.php.net/rfc/callable-types
>
> The W.I.P patch is available for testing through http://3v4l.org under the
> RFC tab.
>
> We count with your detailed feedback and insights. Let's have a nice,
> respectful and
> constructive conversation about the RFC and work on possible improvements!

Very cool to see work on this. The lack of clear signature definition is 
definitely one of the main hurdles to using "callable" in interfaces for 
plugin systems and such where third parties have to integrate.

Not much else to say, the syntax reads a bit weird/heavy being all 
in-line with the function signature but at the same time I can't imagine 
how else it would work that would be any better.

Cheers

-- 
Jordi Boggiano
@seldaek - http://seld.be