The RFC has been moved to the wiki: https://wiki.php.net/rfc/never_for_parameter_types
The most critical points of discussion in my mind are: 1. Should never require **explicit** widening as discussed? This could be very useful but would make it the only case in PHP where omitting a type is not seen as "mixed". (This could be set up as a secondary vote.) 2. If the answer to question #1 is yes, should an error specific to this case be provided instead of the more generic "declaration of A must be compatible with B"? 3. Should we attempt to limit usage of this feature to only interfaces and abstract classes? (NOTE: It's unclear how such a thing would be implemented or if it is feasible.) If it must be available to all function parameters due to implementation, is that acceptable? To clarify, this feature is most critically useful for certain internally provided interfaces, such as ArrayAccess or the proposed interfaces in my draft of Operator Overloads. I'm sure it would find use in user code as well (I know that I would use it in certain interfaces in my own libraries), but it's absence actually makes certain core features very difficult to provide in an intelligent way. Jordan
