arziel's avatar

Arziel

arziel

Member since

136

Total Reputation

2

Total Arguments

10

Total Votes for Arguments

Arguments and votes

1

Just why not :)) No one was forced to use them, but when it's introduce it has many useful applications.

Share:
Read the RFC: Short Closures 2.0 arziel avatar
arziel
voted yes
10

Makes code more clean because it is shorter and the use keyword is not needed anymore.

Share:
Read the RFC: Short Closures 2.0 buismaarten avatar
buismaarten
voted yes
6

As with all other RFC with 'adding' behaviour, if you don't like it, just don't use it and left it for others :))

Share:
Read the RFC: Interface Default Methods arziel avatar
arziel
voted yes
10

Technically writing a trait isn't a showstopper, but it adds cognitive load because the developer now must know/remember using this Interface requires adding this Trait. PHP should focus more on development experience!

Share:
Read the RFC: Interface Default Methods eugen avatar
eugen
voted yes
5

I personally don't need it but I guess it could be useful to people.

Share:
Read the RFC: Interface Default Methods alex avatar
alex
voted yes
8

It will solve having to create traits to add a default implementation when creating interfaces and keeping it nicely together improving the DX

Share:
Read the RFC: Interface Default Methods Carakas avatar
Carakas
voted yes
17

Multi-inheritance seems to be the hot topic that prevented this RFC from being approved even though it was not the RFC target. Multi-inheritance is an afterthought that may or may not be abused with this change. What we want would actually be just the convenience of doing what Traits already allow while reducing potential BC break impact coming from interface changes. There are interfaces originated from the interface segregation mindset that often has only 1 implementation and could very well take advantage of default implementation for a simpler system design.

Share:
Read the RFC: Interface Default Methods marco avatar
marco
voted yes
81

We spend a lot more time reading code than writing it. The elegance of short closure combined with the convenience of variable scope usage has already shown to be a game changer on Typescript and there doesn’t seem to be any technical issue with having it on PHP.

Share:
Read the RFC: Short Closures 2.0 marco avatar
marco
voted yes
120

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
55

I wrote down some thoughts on this RFC on my blog. I think it's worth rethinking our current definition of what "an interface" is. Especially since many languages are interface default methods as their way of multi-inheritance.

Share:
Read the RFC: Interface Default Methods Contributor brent avatar
brent
voted yes
RSS Feed Contribute Watch on YouTube Our License
© 2024 RFC Vote. This project is open source. Contribute and collaborate with us!