Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109885
MIME-Version: 1.0
References: <CANeKSiRbPFbP9GjWdwbQ3J4oLP2wjKGoxnz1EbVb9K0aejg4EQ@mail.gmail.com>
 <CADyq6sLw8tKcqV0ukjbkey5tXEraTk6zzbbTXB8_0_wO0xO6jQ@mail.gmail.com>
In-Reply-To: <CADyq6sLw8tKcqV0ukjbkey5tXEraTk6zzbbTXB8_0_wO0xO6jQ@mail.gmail.com>
Date: Tue, 28 Apr 2020 17:07:14 +0100
Message-ID: <CALKiJKo_ad+dg6nX5Rq8ax5-2hYWTbzkK7+_-rLv5TKTbYrMRw@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000d11ef05a45c0744"
Subject: Re: [PHP-DEV] Renaming PhpAttribute to Attribute
From: rowan.collins@gmail.com (Rowan Tommins)

--0000000000000d11ef05a45c0744
Content-Type: text/plain; charset="UTF-8"

On Tue, 28 Apr 2020 at 16:43, Marco Pivetta <ocramius@gmail.com> wrote:

> `Attribute` is certainly too generic, and will needlessly collide with code
> in the wild.
>


I wonder how true that is, precisely because it *is* so generic, so people
will likely have used it with a prefix or in their own namespace. It might
be interesting to get some stats before burdening the language with more
inconsistency.


> I suggest circling back to the `PHP\` namespace discussion, and having
> `PHP\Attribute` if you really have a problem with current naming.

That would be a second-best, in my opinion; less arbitrary than
"PhpAttribute", but still awkwardly inconsistent with the rest of the
language unless we have plans to move other things that feel like the same
category, such as Throwable, Exception, Closure, etc.


Regards,
-- 
Rowan Tommins
[IMSoP]

--0000000000000d11ef05a45c0744--