specialtactics's avatar

Max

specialtactics

Member since

50

Total Reputation

2

Total Arguments

6

Total Votes for Arguments

Arguments and votes

1

Those parantheses really annoy me

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

I think this is confusing more than anything, plus you can already do this through setters and getters

Share:
Read the RFC: Asymmetric Visibility v2 specialtactics avatar
specialtactics
voted no
16

Every time I find myself typing new MyClass() and than returning back and adding those parentheses. It would be good to reduce this friction and make PHP coding flow smoother.

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

mmh, seems to me that just replacing function by fn and having such a different behaviour is risky

Share:
Read the RFC: Short Closures 2.0 remivasco avatar
remivasco
voted no
24

The 'use' statement clarifies the scope for me. So a proposal like this could have the side effect of mixing scope which would lead to a confusing code.

Share:
Read the RFC: Short Closures 2.0 nabeel avatar
nabeel
voted no
13

I really do not want to see this in PHP because it tempts to apply closures on everything. The question is not if we can but if we should.

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