Hi Derick, sorry, previous message was meant to reply to you. There is no BC break, not even subtle.
Ocramius' assumption is wrong. The most authoritative one is the innermost and closest ancestor definition. It is like that for classes, it is like that for interfaces, should be like that for abstract methods as well. And it's just an assumption anyway. Substitutability rules define this and it is very straightforward to me: are the overridden signatures type-compatible with the super definition? Yes. Then it should be allowed; we should not care if it's redundant, we should not care if it has few uses, just keep it consistent, IMO. Use cases are the same of a type change in a sub-interface, which, again, PHP does allow, even if to/from no-type only for now. Regards.
