On Tue, Jul 22, 2014 at 3:56 PM, Andrea Faulds <a...@ajf.me> wrote: > Ah, I think you misunderstand. What I mean is that we > should only propose RFCs which change the spec > when there is already a working implementation first. > Otherwise, we might add things to the spec which won’t > or can’t get implemented. It would also be best to propose > changes which have been implemented in Zend, to ensure > there is one fully compliant implementation. > Our RFCs tend to have implementations attached to them (in someone's personal fork). IMO we should make creating the spec PR part of the RFC acceptance process, and that they should be landed together. I agree it doesn't make much sense to define unimplemented behavior as the standard.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
