wendell_adriel's avatar

Wendell Adriel

wendell_adriel

Member since

75

Total Reputation

3

Total Arguments

3

Total Votes for Arguments

Arguments and votes

2

Most of the time when creating an Interface that shares some implementation we would always create Interface + Trait. This is just more work. With Interface default methods we would get rid of the Trait and be able to have it in the interface already!

Share:
Read the RFC: Interface Default Methods wendell_adriel avatar
wendell_adriel
voted yes
1

Being possible to create closures that share the scope would be a game changer because it would mean less work and headaches with the use() block that in some cases if you don't pay attention it could lead to a lot of time waste on refactors and maintenance in code.

I think that with this, we would be able to write cleaner code that's easier to understand!

Share:
Read the RFC: Short Closures 2.0 wendell_adriel avatar
wendell_adriel
voted yes
1

This is a pattern already used in some tools and frameworks like Laravel with pipelines and since we have arrow functions and first-class callable I think this would bring a lot of possibilities to the language.

Also this is already proved really handy on other languages.

Share:
Read the RFC: The Pipe Operator wendell_adriel avatar
wendell_adriel
voted yes
RSS Feed Contribute Watch on YouTube Our License
© 2024 RFC Vote. This project is open source. Contribute and collaborate with us!