Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93463
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.53 cause and error)
MIME-Version: 1.0
In-Reply-To: <op.yhw6ft0mc9evq2@nikita-work-box>
References: <op.yhw6ft0mc9evq2@nikita-work-box>
Date: Tue, 24 May 2016 00:24:12 +0100
Message-ID: <CA+kxMuTxYP2n5t5x7B1HH0P8x11mAGJaEsBiG7ncvtDMFmnhCg@mail.gmail.com>
To: Nikita Nefedov <inefedor@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] [Vote] Callable types (now: Callable prototypes)
From: danack@basereality.com (Dan Ackroyd)

Hi Nikita,

On 23 May 2016 at 15:27, Nikita Nefedov <inefedor@gmail.com> wrote:
> With this message I'd like to go to vote
> with the Callable prototypes RFC targeted at 7.1:
> https://wiki.php.net/rfc/callable-types

To explain my vote - I think we definitely need to be able to specify
the signatures of callables in PHP, and I would very probably support
either a 'typedef' RFC, or an expansion of current functional type
(i.e. invokables) to be easier to use with functions, but I just
couldn't possibly vote for an RFC that means people would sometimes
write code similar to this:

    function foo(int $a, int $b,
callable(callable(callable(callable(int, int):int $zebranky, int):int
$pik, int):int $fot, int):int $zot): int {
        return $zot($a, $b);
    }

to use the feature of the RFC.

I realise that is an extreme case, but I think that splitting where a
type is defined (with a name) and the place where it is used to be
separate places, is one of the things that the design of PHP got
right. It makes it easier to read code, even if it makes the language
feel less 'powerful' than other languages.

cheers
Dan