On Wed, 17 Jun 2026 at 11:47, Anton Smirnov <[email protected]> wrote:
> > As for the existing stuff that you mention, we already have this casing > salad anyway even if we simply follow IDE autocomplete > > Yes we do, hence why I would love for this RFC to pass and the standard library be unified by the standards you linked. However, unless compromise is made to do so this RFC would cause more problems than it solves. I think this is really down to a case where PHP has held onto too much legacy problems, and attempts to fix those problems cause more problems. For userland definitions I think this can be adapted quickly to that subsection, because ideally developers should be following the documentation. It doesn't __break__ PHP, it breaks incorrect implementations of userland code and helps enforce good developer behaviour, such as following the definition Eg, if the developer defines `\Movies\ILike\Moneyball` and then the implementer uses \movies\ilike\MoneyBall` then I can agree, that should generate an error Implementations like this: https://3v4l.org/FQKLq I 100% agree, should not be possible. But for internal PHP definitions I'm not sure what a solution would be which does not completely havoc.
