Den 2017-03-24 kl. 21:08, skrev ilija.tov...@me.com:
Hi Rowan
I see. I still think a simple poll would be useful to choose the least
controversial syntax.
Otherwise I fear that the RFC might get rejected out of superficial reasons.
Regards,
Ilija
On 7 Feb 2017, 21:07 +0100, Rowan Collins <rowan.coll...@gmail.com>, wrote:
Hi Ilija,
On 7 February 2017 18:58:15 GMT+00:00, ilija.tov...@me.com wrote:
And also, have you considered letting people vote for their preferred
arrow function syntax?
I kinda don’t think we’re gonna find an agreement as there are so many
different opinions.
The problem with voting on alternative syntaxes is precisely that there *are*
so many different options. Designing a vote with multiple options that gives an
answer people are happy with is a whole science in itself.
I think the best we can do is have a "without prejudice" vote on a single
proposal - if it is declined, a new proposal can be made after a suitable period of
reflection. This has already happened once with this very topic, this RFC having emerged
from a previous one being rejected.
That doesn't mean we can't discuss other syntaxes, but just opening up all
possible options to a vote doesn't really help IMHO.
Regards,
--
Rowan Collins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
My suggestion for a vote would be:
- Vote about the feature.
- Vote about syntax if no consensus can be reached.
My suggestion would be to both have a short and long version:
- |params| => expr
- lambda(params) => expr
An example where one have two syntaxes for same feature is
the jQuery library, i.e. $() and jQuery().
I plan to read up on the RFC once more this week regarding
the feature itself. Any plans to go with this for 7.2?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
