Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88662
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+kxMuSFP=vooMzCYMapTsis6RGBVd-T4YM9z3YuxgF3Rcj6EQ@mail.gmail.com>
References: <CA+kxMuSFP=vooMzCYMapTsis6RGBVd-T4YM9z3YuxgF3Rcj6EQ@mail.gmail.com>
Date: Sun, 4 Oct 2015 07:41:23 -0300
Message-ID: <CADyq6s+16pW=w7S-djTyidxX7pN58Qxxuoyr2FMLDgmicVjfoA@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3ae5ec023260521450980
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION]: Closure from callable
From: ocramius@gmail.com (Marco Pivetta)

--001a11c3ae5ec023260521450980
Content-Type: text/plain; charset=UTF-8

As mentioned already by Andrea: why not just a named constructor on the
closure class, like `Closure::fromCallable(callable $callable)`?
Much simpler, easier to find, etc etc...
On Sep 29, 2015 11:23, "Dan Ackroyd" <danack@basereality.com> wrote:

> Hello internals,
>
> I'd like to start a discussion of a proposal to allow closures to be
> created in user-land without having to use a whole lot of reflection
> code.
>
> https://wiki.php.net/rfc/closurefromcallable
>
> Thanks to Joe and Bob for the assistance in the patch.
>
> cheers
> Dan
> Ack
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a11c3ae5ec023260521450980--