Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108825
MIME-Version: 1.0
References: <CAF+90c8qf5SvKNf0g3JKmgM=QittN-DfxrMqvwgnbztnTGoZvg@mail.gmail.com>
In-Reply-To: <CAF+90c8qf5SvKNf0g3JKmgM=QittN-DfxrMqvwgnbztnTGoZvg@mail.gmail.com>
Date: Tue, 3 Mar 2020 16:00:51 +0100
Message-ID: <CAF+90c_WPw9d2joCFHf33TcV+_Es3n0z1nkQqANjJzrZAjksoQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ccc523059ff4924d"
Subject: Re: [RFC] Validation for abstract trait methods
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000ccc523059ff4924d
Content-Type: text/plain; charset="UTF-8"

On Fri, Feb 7, 2020 at 11:32 AM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I've sent a mail about this before, but as this turned into a bit of a
> larger change (also allowing "abstract private" methods in traits) and
> there's some backwards compatibility impact, I've created a proper RFC for
> this:
>
> https://wiki.php.net/rfc/abstract_trait_method_validation
>

Based on Nicolas' feedback, I've adjusted the RFC to not validate the
visibility of the method (only the signature and "static-ness"). The reason
is outlined in the last paragraph of the Proposal section.

With that done, I plan to open voting on this tomorrow, unless something
new comes up.

Regards,
Nikita

--000000000000ccc523059ff4924d--