Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110813
MIME-Version: 1.0
References: <CA+kxMuRg14XXiYOrDvWygAs+a+mFd2-skYLO6yddnj+9+4w6pw@mail.gmail.com>
 <VE1PR08MB52611174C69F2F00C15CEA74B8B00@VE1PR08MB5261.eurprd08.prod.outlook.com>
 <CA+kxMuR=WqRmOQjc-b2Fxzuk=ecrN7wPmYX5+zUnK4XDgCEkig@mail.gmail.com> <ace53b58-5201-4555-8127-186f48f0a611@www.fastmail.com>
In-Reply-To: <ace53b58-5201-4555-8127-186f48f0a611@www.fastmail.com>
Date: Thu, 2 Jul 2020 11:26:17 +0100
Message-ID: <CA+kxMuS7u-jRr6Yqp_BVGO_z7TYaNpAkuYPjogxG3n0GoqMBqg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Draft RFC callable types + callable type/function autoloading
From: Danack@basereality.com (Dan Ackroyd)

On Wed, 1 Jul 2020 at 20:40, Larry Garfield <larry@garfieldtech.com> wrote:

> it would also offer a way to do effectively the same thing

One use-case that would need to be covered for that would be for
callables where you don't know how many parameters there would be in
the callable.

> duplicate functionality needlessly.

Good chance it might still be nice. Not only is the syntax a little
bit nicer imo:

// For some class
class Foo {
    public static function quux() {
        echo "I am quux";
    }
}

// Partial version
[Foo::class, 'quux'](?);

// Dedicated version
$(Foo, quux);

As I find it easier to read, but also avoiding using strings to
reference functions/classes is probably less ambiguous for both humans
and computers.

cheers
Dan
Ack