On Saturday, 15 March 2025 at 09:23, Juris Evertovskis <ju...@glaive.pro> wrote:
> On 2025-03-14 10:09, Juris Evertovskis wrote: > >> Hello, >> >> I’ve opened the vote on the Optional interfaces RFC. >> >> https://wiki.php.net/rfc/optional-interfaces >> >> Implementation: https://github.com/php/php-src/pull/17288 >> >> Discussion: https://externals.io/message/126185 >> >> The voting will be closed on 2025-03-29 00:00:00 UTC. >> >> BR, >> >> Juris > > Hello again, > > A reddit discussion has started as well: > https://www.reddit.com/r/PHP/comments/1jbcbtx/php_rfc_optional_interfaces/ > > It might be useful to those who haven't made their minds up yet. It contains > a lot of opinions with both criticism and usecases of this feature. > > The key point, hoewever, seems to be that the naming of the feature is > excremental and very easy to misunderstand. I suppose the naming issue can be > solved separately (if a better name is found) and the documentation can use a > different naming and description if the RFC itself passes. Frankly, the comment from u\phuncky [1] mentioning the possibility of bad interactions with default interface methods (something I think is more important than this) is reinforcing my opinion that this RFC solve the problem in a bad way. And another user [2] was basically suggesting my previous solution of adding support for type classes/runtime implementation of interfaces. Best regards, Gina P. Banyard [1] [https://www.reddit.com/r/PHP/comments/1jbcbtx/comment/mhtpwa2/](https://www.reddit.com/r/PHP/comments/1jbcbtx/comment/mhtpwa2/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) [2] [https://www.reddit.com/r/PHP/comments/1jbcbtx/comment/mhvxo5j/](https://www.reddit.com/r/PHP/comments/1jbcbtx/comment/mhvxo5j/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
