hi Andrea, On Mon, Sep 15, 2014 at 3:07 PM, Andrea Faulds <a...@ajf.me> wrote: > > On 14 Sep 2014, at 00:35, Andrea Faulds <a...@ajf.me> wrote: > >> I have postponed the vote after further thought. It’s been a while since >> this was discussed on the list. >> >> However, it is my intent to open voting properly at some point soon, if all >> goes to plan. > > I have withdrawn the RFC. I do not feel anymore that it is the way forward > with scalar type hints in PHP.
Sigh. Here we go again. I do not think we will ever reach an agreement on the list before the RFC goes to the voting phase. That's why I think the RFC should contain the most requested options and go with them. Any further discussions will simply create more confusions and yet again move to a dead end, we all lose. It would be great if there are two sets of options: - One about having scalar typed arguements, hinted or not, simple yes/no, so we at least agree on having the feature - a set of options about how should it work . strict . what the rfc describes in its last state . matching, if possible at all, current casting, following what (int)$foo and co or whatever is considered as "the common casting php way" I am not saying these are the only options or only the correct ones, there may be other. I only would like to get this sorted out sooner rather than later. If we agree on the feature itself and we do not see a clear majority on one point or another, let take the top two options and try to figure what has to be changed to get a majority (2nd phase vote). To be more clear: We must get a decision here. I am convinced that this is a top requested feature, since very long. Delay it forever only because we are unable to find a concensus sounds pretty bad. Let get us together to finally have this feature implemented, in the best possible way. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
