On Tue, 20 Jun 2023, 04:10 Levi Morrison, <le...@php.net> wrote: > > I like the idea of this RFC - in fact it's one which has been near top of > > my wishlist for PHP language features for a long time - but I think this > is > > an issue with the proposed implementation which at the very least > warrants > > highlighting and discussion. > > I understand your concern but personally believe it's overblown. This > problem already exists with abstract classes, but doesn't seem to be > that much of an issue in practice. I hope static analysis can fill the > gap here, but don't think these checks are necessary to ship this > feature. >
Yeah I suppose I'm just saying "Interface default methods" can be interpreted a few different ways and there's key differences between Java-style, versus syntax sugar for mixing an interface and a trait in to one unit, versus a user can effectively extend multiple abstract classes but with interface keyword. Appreciate it appears to still be a WIP and you may not have decided or designed all the finer details yet but I think at the very least, the RFC text needs to be updated as soon as practical to be much more explicit about these details so voters know exactly what they're voting on when the time comes. Cheers. >
