Hi! >> On 17 Dec 2014, at 01:32, Stanislav Malyshev <smalys...@gmail.com> >> wrote: >> >> Hi! >> >>> AIUI, this RFC is meant to introduce some sugar only. Wouldn't >>> it be >> >> I'm not sure what you mean by "some sugar only". It introduces the >> capability of using objects in array key context, which was not >> available until now. > > That’s not true: the RFC doesn’t allow objects to be keys,
And reading what I actually wrote would reveal that I did not write "allow objects to be keys", I wrote "using objects in array key context", and this is of course true. Please do read what you calling "not true" before doing it. I explained it numerous times, I even wrote a special blog post explaining it, I referenced it here, but it as if nobody is actually reading anything before repeating the same arguments. > it just adds implicit conversion. This is just sugar for an explicit > conversion to int or string. And this is completely false. While the result of the function must be int or string, saying any function that returns int or string is "just sugar for an explicit conversion to int or string" is false. This function has its separate purpose which does not equal converting to any specific type, but is suited for its unique context. You _can_ have it return the same result as (int) or (string) but you don't have to. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
