Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93467
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.48 as permitted sender)
Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes
To: internals@lists.php.net, "Markus Fischer" <markus@fischer.name>
References: <op.yhw6ft0mc9evq2@nikita-work-box>
 <BLU436-SMTP126DBF5249BC1762E4DE471E24E0@phx.gbl>
 <op.yhxkcgp5c9evq2@nikita-pc>
 <02cd6780-5113-3c37-2ae7-75f9a8465b63@fischer.name>
Date: Tue, 24 May 2016 09:01:27 +0300
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Message-ID: <op.yhydopzac9evq2@nikita-pc>
In-Reply-To: <02cd6780-5113-3c37-2ae7-75f9a8465b63@fischer.name>
User-Agent: Opera Mail/12.17 (Win32)
Subject: Re: [PHP-DEV] [RFC] [Vote] Callable types (now: Callable prototypes)
From: inefedor@gmail.com ("Nikita Nefedov")

On Mon, 23 May 2016 22:59:10 +0300, Markus Fischer <markus@fischer.name>  
wrote:

> Hello Nikita,
>
> On 23.05.16 21:27, Nikita Nefedov wrote:
>> 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.
>
>
> I like the RFC, however I do not like this behavior.
> This would behave differently then how current weak/strict mode works.
>
> I was never a fan of the weak mode to begin with, but now introducing
> something which deals in the area of argument passing and not behaving
> to what a 2/3 majority agreed is IMHO a no-go. The current RFC does not
> even mention that.
>
> Maybe it's not feasible anyway, but in any case I'm missing
> input/discussion in this area.
>
> - Markus
>

Morning Markus,

Well, those strict/weak modes were initially invented for basic types,
not for composite types so I'd question if their support is needed at  
all...

For example regardlessly of what mode your file in, if you implement
an interface with `function foo(int $b)` you'd always have to implement
it with `int`, and not `float`.