Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93454
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.180 as permitted sender)
Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes
To: "internals@lists.php.net" <internals@lists.php.net>
References: <op.yhw6ft0mc9evq2@nikita-work-box>
 <BLU436-SMTP126DBF5249BC1762E4DE471E24E0@phx.gbl>
Date: Mon, 23 May 2016 22:27:42 +0300
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Message-ID: <op.yhxkcgp5c9evq2@nikita-pc>
In-Reply-To: <BLU436-SMTP126DBF5249BC1762E4DE471E24E0@phx.gbl>
User-Agent: Opera Mail/12.17 (Win32)
Subject: Re: [PHP-DEV] [RFC] [Vote] Callable types (now: Callable prototypes)
From: inefedor@gmail.com ("Nikita Nefedov")

Hi Bob,

When you pass an `int` to a `string` type parameter in weak mode
it's being coerced to the needed type (not just directly passed).

This is quite complex, because you'd need to copy zend_function
and all its members (without changing the original zend_function).

I would love to support it but all in all it comes down to
implementation here for me, so I'd rather do it in a separate
RFC.

If you meant accepting `function(string $foo){}` as an argument
of `callable(int)` parameter without coercing then this would
be impossible due the fact that this all is context-dependent.
Which means that the function which got `function(string $foo){}`
in place of `callable(int)` could itself be strict-mode
and when it would call this function it would raise a TypeError.


On Mon, 23 May 2016 20:05:50 +0300, Bob Weinand <bobwei9@hotmail.com>  
wrote:

> 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>:
>>
>> Evening internals,
>>
>> 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
>>
>> 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.
>>
>> 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)