Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82532
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
In-Reply-To: <54DC788E.7000000@hoa-project.net>
References: <CAOsHV+t=peeRbvXtDoPL2EnvWsQVHNtNYJ5h_e9VQLeLq-srDA@mail.gmail.com>
 <54DC788E.7000000@hoa-project.net>
Date: Thu, 12 Feb 2015 10:21:02 -0300
Message-ID: <CAOsHV+tcaUZe+siZA7J=Ym2JGyUS7m+z3Q2M6Aav4R=4FssM9w@mail.gmail.com>
To: "Ivan Enderlin @ Hoa" <ivan.enderlin@hoa-project.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3c9660f49f7050ee3ff94
Subject: Re: [PHP-DEV][RFC][VOTE] Group Use Declarations
From: marcio.web2@gmail.com (Marcio Almada)

--001a11c3c9660f49f7050ee3ff94
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> Thanks for the RFC!
> We discussed a little bit with the Hoa [1]'s and fruux [2]'s community
and we have a question.
> Why not pretending we have an array of symbols, something like:

>    use Foo\Bar\[Baz, Qux];

> instead of

>    use Foo\Bar\{Baz, Qux};

> This is a list vs. block debate. While I personally would go for `{` and
`}`, here we declare a list, so we guess the array syntax
> would be more tailored.
> Thoughts?

Hi,

This is an interesting one. During research, the `[` and `]` syntax was
considered for a while but it quickly felt apart for the following reasons:

1. Most people considered on PHP the array construct is a very important
building block and therefore we should avoid to multiplex or reuse its
syntax in multiple contexts. This becomes more clear in cases involving
conflict resolutions:

use Foo\Bar\[Baz *as* Buz, Qux\Quaz *as* Quiz];

2. Block syntax seemed more versatile and prone to reuse because we already
have the traits conflict resolution syntax:

http://php.net/manual/en/language.oop5.traits.php#language.oop5.traits.conf=
lict

The reasoning for using commas to delimit imported entities and not `;` is
that current use declaration syntax is a comma separated list:

use function foo\math\sin, foo\math\cos, foo\math\cosh;

Hence the `{..., ...}` syntax seemed the most tailored to feel similar and
obvious for most of the current PHP userbase, based on all experiments:

use function foo\math\{ sin, cos, cosh };
use function Foo\Bar\{ A, B as Baz, C };

I hope that the given information is useful to your decision process. Good
voting!

Sincerely,
M=C3=A1rcio Almada.

--001a11c3c9660f49f7050ee3ff94--