Re: [VOTE][RFC] Closure::call()
| From: | Andrea Faulds | Date: | Tue, 19 Aug 2014 00:04:09 +0000 |
| Subject: | Re: [VOTE][RFC] Closure::call() | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-76674@lists.php.net to get a copy of this message | ||
On 18 Aug 2014, at 00:40, Levi Morrison <levim@php.net> wrote:
> On Sun, Aug 17, 2014 at 5:13 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>> Hi!
>>
>>> It does, but maybe you missed it. Under the Proposal section:
>>>
>>>> To solve this, we relax the current invariant of scoped closures
>>>> having to be bound, and add a new parameter to bind(To) to produce
>>>> an unbound, scoped closure, like so:
>>
>> Indeed, I missed it - I was looking for bindTo. I think it should be
>> made more prominent, and I'm not sure what closure that is not static,
>> but does not have a bound object, means. What happens if you call it? It
>> sounds a bit strange concept - why would you need a closure that is not
>> static, but is not bound to any object?
>
> Hence the vote was cancelled while it is reworked.
To clarify: The RFC has been reworked now, I actually changed the RFC and patch just before I
cancelled the vote. Review appreciated before vote is reopened.
--
Andrea Faulds
http://ajf.me/