Hi
On 5/22/23 23:32, David Gebler wrote:
whether there's an appetite out there in general to start adding all sorts
of new runtime checks, which I would argue means any new runtime check
warrants the utmost consideration of cost-benefit.
Just to make sure there is no misunderstanding I'd like to clarify that
the proposed check of this RFC is not a runtime error. It's a compile
time error, just like the check for incompatible method signatures
during inheritance. In fact it shares a non-trivial amount of the
existing logic of that check, because it's so similar.
My understanding is that once the class is successfully sitting in
Opcache there will not be any further overhead.
------
With regard to the rest of the email, I (naturally?) disagree that this
should not be part of the language itself. I currently have less time
available than expected, I'll put the email back on unread and hope to
be able to give a more expanded and nuanced reply later. I just wanted
to get the first part with regard to runtime vs. compile time out for now.
Best regards
Tim Düsterhus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
