Hi internals,
I'd like to start the discussion for a new RFC about being able to mark
interfaces as deprecated.
- RFC: https://wiki.php.net/rfc/deprecated_interfaces
- Implementation: https://github.com/php/php-src/pull/21998
Thanks,
-Daniel
Hi internals,
I'd like to start the discussion for a new RFC about being able to mark
interfaces as deprecated.
- RFC: https://wiki.php.net/rfc/deprecated_interfaces
- Implementation: https://github.com/php/php-src/pull/21998
Thanks,
-Daniel
I somehow didn't even realize this wasn't already supported from the beginning. Yes, this is an obvious addition.
--Larry Garfield
Hi
I'd like to start the discussion for a new RFC about being able to mark
interfaces as deprecated.
- RFC: https://wiki.php.net/rfc/deprecated_interfaces
- Implementation: https://github.com/php/php-src/pull/21998
I could swear that the discussion for this RFC had already started,
perhaps it was just mentioned as future scope or got a passing mention
in some other discussion instead. Anyway :-)
-
There is a typo in the “Comparison” table: You dropped the
pin
“ImlementsBase” (and the others). -
I just added the “Abstain” option to the widget for you. The RFC
probably predates that policy change. -
The proposal makes sense to me and I agree that there is no room for
further “improvements” regarding deprecating interfaces. Extending an
interface and implementing an interface is the two places where an
interface actively gets used.
Neither instanceof or using an interface in a type declaration should
warn, since there is no way to avoid the deprecation there without
actually making a breaking change. Those are “passive” consumers of an
interface. It probably makes sense to at least spell out in the RFC how
these consumers were considered and why they don't emit the deprecation
notice.
Best regards
Tim Düsterhus