Hi! > the wall. By deciding not to include this in PHP 7.3, we are essentially > making an implicit decision that PHP 7.4 is going to be a relatively > ordinary feature release rather than a deprecation-only one. (Which is fine > by me really, I don't like the idea of a release that's all stick and no > carrot.)
I am completely fine with that too. I don't see why 7.4 should be deprecation-only if we have new pending features that are ready by 7.4. > Finally, given the current situation where we have a whopping five (!!) > RFCs with votes ending the day before feature freeze, I'd say postponing > the schedule is a good idea even without any consideration to typed > properties. Just landing something like the comparison overloading RFC on > the day of feature freeze is not going to be pretty. We are quite obviously I would be also against that, but the current voting pattern suggest the vote may make the question moot anyway. That said, typed properties are IMO much larger than comparison overloading RFC, which is still a bit niche. I would be most happy to have both in 7.4 if they pass, but I don't think it would be a major problem if comparison overloading one is passed and we delay 7.3 a bit to accommodate it. But for typed properties I think we should just target 7.4 and not even consider rushing with it. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
