Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108914
MIME-Version: 1.0
References: <CAEPJdunSr8PkBtSLO8g_JMLzM4cFVnXsQSEMFmu2RN25XT=grw@mail.gmail.com>
In-Reply-To: <CAEPJdunSr8PkBtSLO8g_JMLzM4cFVnXsQSEMFmu2RN25XT=grw@mail.gmail.com>
Date: Mon, 9 Mar 2020 17:17:31 +0000
Message-ID: <CALKiJKqit6xcZtDVzCjbHtd9Sxs+_aFLfUgSnFcaGsje_9tw8w@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000068219e05a06f2eb6"
Subject: Re: [PHP-DEV] [RFC] Attributes v2
From: rowan.collins@gmail.com (Rowan Tommins)

--00000000000068219e05a06f2eb6
Content-Type: text/plain; charset="UTF-8"

Hi Benjamin

On Mon, 9 Mar 2020 at 14:43, Benjamin Eberlei <kontakt@beberlei.de> wrote:

> I want to resurrect Dmitrys Attributes RFC that was rejected for 7.1 in
> 2016 with a few changes, incorporating feedback from the mailing list back
> then and from talking to previous no voters.
>
> The RFC is at https://wiki.php.net/rfc/attributes_v2
>


Thanks for picking this up again. It's amazing how deeply the integration
of annotations has embedded into PHP without any support from the language,
so this feels long overdue.

One quick suggestion: the use cases currently appear inside the Proposal
heading in the RFC, and some but not all are labelled "not part of the
RFC". It might be useful to have a clearly separate "Possible Use Cases"
header, and a summary somewhere of which interfaces and classes would
actually be provided by the initial implementation.

Regards,
-- 
Rowan Tommins
[IMSoP]

--00000000000068219e05a06f2eb6--