Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111105
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2007221247530.7489@singlemalt.home.derickrethans.nl>
In-Reply-To: <alpine.DEB.2.23.453.2007221247530.7489@singlemalt.home.derickrethans.nl>
Date: Wed, 22 Jul 2020 14:30:29 +0200
Message-ID: <CABdc3WpRLzG5yvL_9dBxjk7G5crVEmbYTZ_qvg3VXXjHtrbVVw@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006d938005ab06e863"
Subject: Re: [PHP-DEV] The @@ is terrible, are we sure we're OK with it?
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--0000000000006d938005ab06e863
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Derick,

=C5=9Br., 22 lip 2020 o 14:00 Derick Rethans <derick@php.net> napisa=C5=82(=
a):

> Hi all,
>
> I know we've voted twice on this already, but are we really sure that
> the @@ syntax is a good idea?
>
> - There are lots of grumbles, both on here, room 11, as well as in the
>   wider community (https://www.reddit.com/r/PHP/comments/hjpu79/it_is/)
> - It has the distinct possibility to cause further parsing issues, akin
>   to what ended up happening with what Nikita is addressing at
>   https://wiki.php.net/rfc/namespaced_names_as_token
> - There is no "end symbol" to make finding occurences easier.
> - It is a syntax *no other language* uses.
> - @ is never going to go away, so the possibility of @@ moving to @ is
>   also 0.
>
> Please, let's do the sensible and use the Rusty #[...] syntax.
>

I agree with all the above arguments.

Is there a place (before feature-freeze) and a way to revote it?
What should be the procedure then?
Does it mean the RFC process has an issue and how could it be fixed?

Cheers,
Micha=C5=82

--0000000000006d938005ab06e863--