Hi Nikita,
For the record, I've voted against this proposal because I believe it
should have gone with option 2, that is to *always* make anonymous
classes final.
It makes very little sense to me that everyone needs to explicitly
mark their anonymous classes as final just because there is a
class_alias loophole that could, in theory, have been used to extend
anonymous classes in the past. Especially given that there is no
evidence of this "feature" being used in the wild (or if there is such
evidence, it was not presented in the proposal).
Should I amend the RFC, recreating the current poll with three mutually
exclusive options (final anonymous classes, final by default without
open, final by default with open) instead of just Yes/No (I personally
share your PoV, but given the minor pushback received in the last
discussion thread I initially decided against it), could that be done
without restarting the discussion process?
Regards,
Daniil Gentili.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
