Re: RFC [Discussion]: Marking overridden methods (#[\Override])
| From: | Tim Düsterhus | Date: | Mon, 12 Jun 2023 15:24:47 +0000 |
| Subject: | Re: RFC [Discussion]: Marking overridden methods (#[\Override]) | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120558@lists.php.net to get a copy of this message | ||
Hi
On 5/11/23 18:37, Tim Düsterhus wrote:
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/9836Discussion has died down, unfortunately without (much) commentary with regard to Claude's and Sara's suggestions. However I believe that the proposal is in a state where is brings a real benefit and where it is also extensible in the future, e.g. to include Claude's "No implicit override" suggestion. I have included it in the "Future Scope" section. Sara's first proposal to make it a LSP check bypass I have added to the "rejected features" section, as argued in my previous response to it. I've also added references for Swift and Kotlin, as these languages where mentioned in PHP Core Roundup #13 by The PHP Foundation. I plan to start the vote later this week, possibly on Wednesday. Best regards Tim Düsterhus