Re: [VOTE] Shorter Attribute Syntax Change

From: Date: Sat, 15 Aug 2020 11:52:48 +0000
Subject: Re: [VOTE] Shorter Attribute Syntax Change
References: 1 2 3 4 5 6 7 8 9 10 11 12 13  Groups: php.internals 
Request: Send a blank email to internals+get-111535@lists.php.net to get a copy of this message
Den 2020-08-14 kl. 21:23, skrev Derick Rethans:
On Fri, 14 Aug 2020, Sara Golemon wrote:
Derick was trying to be good and meet my beta3 deadline.
And I even got that date wrong by a week. Oops.
Fortunately, I gave him that deadline (while thinking RC1) knowing some kind of bullshit like this would come up and LO AND BEHOLD here we are. So the good news is that we actually have a spare two weeks. On Fri, Aug 14, 2020 at 7:22 AM Theodore Brown <theodorejb@outlook.com> wrote:
2. Include a ranked voting option for @: and mention its pros and cons (it is equally concise as @@ with no BC break, but is somewhat harder to type). Patch link: https://github.com/theodorejb/php-src/pull/1
Glancing at beberlei's reply, I do agree that @: is coming slightly out of left field. However, we're using a STV system, so might as well go wild with the options (within reason). HOWEVER, any option included is going to need the same care applied as you outline in #3 and #4 below.
I would like to point out that as the main premise of the RFC was that the chosen syntax had no ending delimiter, I would say that any new suggested syntax should have one before I would be willing to consider adding it.
I think that lack of ending delimiter is not a good enough reason to exclude the @: syntax from the RFC and voting. Would be good to have the community view on this in order to put this to rest! We have the @@ syntax in the voting and of course that's natural. Still adding the @: option would in my eyes give a more complete view of feasible syntax choices. The far fetched ones should not be included of course. r//Björn L

« previous php.internals (#111535) next »