Voted "no" because of this paragraph: > This RFC proposes to allow this, even if it has very few uses, and because there is no reason to disallow a compatible redefinition.
I couldn't see a use-case. In addition to that, this breaks the assumption that the topmost abstract signature is the authoritative one. That is a subtle BC break, but still a BC break. Yes, I know I'm annoying, sorry 😥 On 28 Mar 2017 01:51, "Wes" <netmo....@gmail.com> wrote: Hello PHPeeps, There hasn't been much discussion around the proposed feature, and I've interpreted it as a good sign :P It is not a super important change but it has some advantages, it's consistent with the recent improvements to type variance and also with future ones. Also, it's hopefully not too hard to implement. https://wiki.php.net/rfc/allow-abstract-function-override I've decided to start the vote. It will end two weeks from this message, on 10th April 2017. Thanks in advance for participating. Wes
