On Thu, 11 May 2023 at 17:37, Tim Düsterhus <t...@bastelstu.be> wrote: > > Hi > > I'm now opening discussion for the RFC "Marking overridden methods > (#[\Override])": > > I'm now opening discussion for the RFC "Marking overridden methods > (#[\Override])":
This RFC is probably a good idea, even if the number of people who will benefit from the behaviour in the engine might be quite low. My guess is the number of people who will bother to write those attributes, and who also won't bother to setup CI, is quite small. But, this RFC another step forward from where we are, to having 'too many' attributes/annotations, so I have a question. How do we stop prevent ourselves from copying the problems that Java has made for itself? Or putting it another way, is it possible for us to set any guidelines on what annotations are 'good' or 'bad' ? I hope I am at least consistent with my concerns about annotations. Danack wrote in https://externals.io/message/114116#114196 > > I think I disagree with this very strongly, and plan* to vote against > any RFC that embeds another language in annotations.** > https://blog.softwaremill.com/the-case-against-annotations-4b2fb170ed67 cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
