Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93452
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.99 as permitted sender)
Message-ID: <BLU436-SMTP126DBF5249BC1762E4DE471E24E0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
In-Reply-To: <op.yhw6ft0mc9evq2@nikita-work-box>
Date: Mon, 23 May 2016 19:05:50 +0200
CC: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
References: <op.yhw6ft0mc9evq2@nikita-work-box>
To: Nikita Nefedov <inefedor@gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Vote] Callable types (now: Callable prototypes)
From: bobwei9@hotmail.com (Bob Weinand)

Hey,

I have a question regarding strict/weak types.

Currently, you cannot pass a callable function(string $foo) {} to a =
signature requiring (callable(int)), if I understood the code correctly.

But weak types actually should allow that as it's totally fine to pass =
an integer to a string in weak mode.

Is there any particular reason to this seemingly arbitrary restriction?

Bob

> Am 23.05.2016 um 16:27 schrieb Nikita Nefedov <inefedor@gmail.com>:
>=20
> Evening internals,
>=20
> 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
>=20
> We've renamed it (previously was "Callable types") as RFC names often
> dictate how users will call the feature and I want it to be more
> accurate/descriptive.
>=20
> Also the reflection part was added although I'm short on time =
currently,
> so implementation for that will be ready later. (speaking of =
implementation,
> it also currently doesn't use cache_slots - also something I'll add =
when
> I have a little bit of time)
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20
>=20