Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111469
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2008100935570.7489@singlemalt.home.derickrethans.nl>
In-Reply-To: <alpine.DEB.2.23.453.2008100935570.7489@singlemalt.home.derickrethans.nl>
Date: Tue, 11 Aug 2020 09:54:29 -0500
Message-ID: <CAESVnVqvVG4dXDbj25YyA4tK=7v0HiEuNbMDZTBCDuAwqSGH0g@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002aca7105ac9b4058"
Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change
From: pollita@php.net (Sara Golemon)

--0000000000002aca7105ac9b4058
Content-Type: text/plain; charset="UTF-8"

On Mon, Aug 10, 2020 at 3:41 AM Derick Rethans <derick@php.net> wrote:

> https://wiki.php.net/rfc/shorter_attribute_syntax_change#voting
>
>
Just chiming in to say all, y'all voting for @[...] are making a terrible
choice, and are you sure you're okay with it?

We have options with varying degrees of backward compatibility issues (<<>>
none, @@ some, #[..] and @[..] a bit more than some), and only one which
offers forward compatibility (#[..]).
So why vote in favor of the option with the highest BC breaking probability
and no FC?

Thank you for coming to my TED talk.

-Sara

--0000000000002aca7105ac9b4058--