tomsix's avatar

tom@webatvantage.be

tomsix

Member since

65

Total Reputation

2

Total Arguments

5

Total Votes for Arguments

Arguments and votes

3

Cleaner code

Share:
Read the RFC: new MyClass()->method() without parentheses tomsix avatar
tomsix
voted yes
1

Interface should not contain implementations

Share:
Read the RFC: Interface Default Methods tomsix avatar
tomsix
voted no
17

In combination with Asymmetric visibility this will allow to replace all getters and setters with trivial properties and occasional hooks.

Share:
Read the RFC: Property Hooks pronskiy avatar
pronskiy
voted yes
75
  • 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
Share:
Read the RFC: Interface Default Methods victor avatar
victor
voted no
121

At least once a week, I throw away an array_map because it ended up looking too bloated and go with a classic foreach instead. Short Closures 2.0 without the use(...) block would've solved this problem, just 2 votes...

Share:
Read the RFC: Short Closures 2.0 davi avatar
davi
voted yes
RSS Feed Contribute Watch on YouTube Our License
© 2024 RFC Vote. This project is open source. Contribute and collaborate with us!