raszekster's avatar

raszekster

raszekster

Member since

110

Total Reputation

5

Total Arguments

6

Total Votes for Arguments

Arguments and votes

1

Looks cool. Hope it does not have weird problems and will not affect performance.

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

This rfc is needed to remove setters and getters. I hope that ability of use property hooks will be added to doctrine cause I hate entities with 1k lines of code just with setters and getters.

Share:
Read the RFC: Property Hooks raszekster avatar
raszekster
voted yes
1

Very good proposal but there are bad examples in RFC. RFC should not use strings as callable.

Share:
Read the RFC: The Pipe Operator raszekster avatar
raszekster
voted yes
88

With First-class callable syntax available since 8.1, it would now be possible to write it as below, which is much better then string names of functions:

$result = "Hello World"
    |> htmlentities(...)
    |> str_split(...)
    |> fn($x) => array_map(strtoupper(...), $x)
    |> fn($x) => array_filter($x, fn($v) => $v != 'O');
Share:
Read the RFC: The Pipe Operator pronskiy avatar
pronskiy
voted yes
4

Since we have already autocaptures for one liners there should be also option for multiple liners.

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

This RFC could be useful if in PHP there was no inheritance and traits. But PHP has both traits and inheritance so this should be used.

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