Piotr Filipek

There is a chain of responsibilities patter that does exactly the same, so I don't see any reason to implement this.

This RFC introduces a mess, because the implementation must be separated from the contract. As someone said: "if multi-inheritance is the subject, a specific RFC shall be done on this".

• Interface shall stay light, pure contracts defining expectations, else they are just abstract classes with multi-inheritance.
• If multi-inheritance is the subject, a specific RFC shall be done on this.
• An other away might be to dig back this RFC to add interface to traits: https://wiki.php.net/rfc/traits-with-interfaces

It looks pretty much the exact function as abstract class. I still think interfaces/contracts should not include any concrete implementation

1. Separation of what (interface) and how (class/trait)
2. More balanced vote chart, now it's too green