Arvids,
I’m afraid you’re still more naive than I am. Don’t you understand it’s dead ? Even before Sara took over 0.3, they decided to revive Andrea’s v 0.1 with no change. The fight will take place between both. Our only right is to enlist in one camp and yell with the mass. We intended to explore missing hints, union types, ZPP conversions. They just want to talk about the declare() syntax. Do you see the gap ? Oh yes, if you insist, you will be told all your concerns are premature. You will work on that later, when BC makes it impossible, or wait for 8.0. I was surprised we could have a window to propose something creative, focusing on other concerns than this stupid declare() J. Imagine, we could have proposed something *without* a declare(). It would have been terrible. All this energy lost arguing about an unneeded directive ! Now, it’s clear. Declare() strikes back ! I know that’s frustrating but I also guess that our work would have been useless as everything would have been rejected. So, it may be better this way. Just enjoy the upcoming show. It has started already. Regards François De : Arvids Godjuks [mailto:arvids.godj...@gmail.com] Envoyé : mardi 17 février 2015 01:17 À : Sara Golemon; francois Cc : Philip Sturgeon; Jefferson Gonzalez; Rowan Collins; PHP internals Objet : Re: [PHP-DEV] Reviving scalar type hints Might I remind everyone that time is not on our side here - feature freeze is looming and actual work has to be done. The part you must understand is: Strict type hints are possible if someone cares to implement them with a next RFC. Be our guest. Right now we need to sort out the basic stuff - the missing numeric/mixed/resource hints, the ability to define mixed hints and make it all consistent. Maybe even fix/change some of conversion rules as a result (i'm just giving an example here). Gives us some time to gather our thought, discuss stuff and do the update to the RFC. Asuming stuff and pointing fingers before new version is out is just distracting.
