On 3/28/2017 6:50 AM, Wes 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 >
There is absolutely no BC break at all in this RFC. The current status of things makes no sense because it is inconsistent. Heck, even the fact that it is inconsistent shows that there are different rules for the same things. Semantically there is no difference between a class, an abstract class, or an interface. They are all classes, some simply omit implementation details and leave it to their subclasses. I hope this gets a yes, regardless of possible use cases, this is simply applying proper variant rules everywhere. -- Richard "Fleshgrinder" Fussenegger -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
