Re: RFC [Discussion]: Marking overridden methods (#[\Override])
| From: | Marco Pivetta | Date: | Thu, 18 May 2023 08:12:28 +0000 |
| Subject: | Re: RFC [Discussion]: Marking overridden methods (#[\Override]) | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120336@lists.php.net to get a copy of this message | ||
Hey Tim,
On Thu, 11 May 2023, 18:37 Tim Düsterhus, <tim@bastelstu.be> wrote:
> Hi
>
> I'm now opening discussion for the RFC "Marking overridden methods
> (#[\Override])":
>
> ----
>
> RFC: Marking overridden methods (#[\Override])
> https://wiki.php.net/rfc/marking_overriden_methods
>
> Proof of concept implementation is in:
>
> https://github.com/php/php-src/pull/9836
The idea is neat, but the trend is roughly:
* Many moving to
final classes (finally!)
* Moving to less methods in an interface (some RFCs around functional
interfaces, even)
I am not sure this RFC is really relevant: I can see some use in generated
code, since this would act as an engine-level checksum for some minimal
changes, but otherwise it's a bit bloated?
Would it perhaps make sense to have this in userland first, in phpstan or
psalm plugins, to see if there is interest?