On 15 March 2015 at 00:54, Niklas Keller <m...@kelunik.com> wrote: > Morning, > > I'd like to announce that I'll open the vote for the in operator later that > day. > You can find the RFC here: https://wiki.php.net/rfc/in_operator
We've discussed this elsewhere and the RFC is still lacking one thing - any justification of why this deserves being a new piece of syntax, rather than just being a function implemented either internally, or even better in userland PHP. I think that adding new syntax for something that could just be a function is not a good idea at the best of times, but when it's such generic keyword that could be far more useful in other places (e.g. Linq style queries) it really needs to have a strong justification. The equation is not just "will PHP be better with this" instead it's "will PHP so much better that it justifies the known cost of adding syntax to the language, as well as the unknown cost of blocking future use of the 'in' keyword". I'm sorry, but I just can't see that the value in adding this comes anywhere close to justifying it's addition. cheers Dan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
