Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92432
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.215.67 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <571532B2.3050900@gmail.com>
References: <CAL=_i_mzF5U4kb487igLrMPvnK5UUNP0W1FA+MYHWMjmypJ3Cg@mail.gmail.com>
	<571532B2.3050900@gmail.com>
Date: Mon, 18 Apr 2016 17:37:27 -0700
Message-ID: <CAESVnVrq1_N7tjSJ5ue=QhOOWuYx_w6MaPg7dN_z_njnX5es-w@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Joe Watkins <pthreads@pthreads.org>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: Functional Interfaces
From: pollita@php.net (Sara Golemon)

On Mon, Apr 18, 2016 at 12:17 PM, Stanislav Malyshev
<smalyshev@gmail.com> wrote:
> Hi!
>
>>     Please review the following RFC:
>>     https://wiki.php.net/rfc/functional-interfaces
>>     An implementation is provided, and is testable on 3v4l.
>
> This looks like a rather narrow case already covered by anonymous
> classes. Am I missing something? What is the added value of it that
> can't be done now?
>
I thought Joe covered that question pretty thoroughly by his countable
examples.  The version using anonymous classes certainly *works*, but
it's significantly more boilerplate code and has a higher cognitive
overhead compared to the functional interface example which is concise
and to the point.

That said, I'm not sure what I'd use it for, but as syntactic sugar
goes it's quite sleek.

-Sara