On Tue, 7 Jul 2020 at 15:47, Larry Garfield <la...@garfieldtech.com> wrote: > > This has reached the 2 week mark, but there's not been much discussion.
Unless I'm having a massive reading failure, this RFC has been announced twice. And feedback was provided before: https://externals.io/message/109646#109647 https://externals.io/message/109646#109648 >From the RFC: > Every new global class, however, creates a potential namespace collision > with existing user-space code and thus a potential for backward > compatibility breaks. This doesn't appear to be an actual problem for the PHP ecosystem. The vast majority of code in libraries is in namespaces, which avoids there being a problem that needs addressing. > Anyone else want to weigh in? I still don't think this RFC is a good way to improve the general situation of PHP. Rather than having more rules (quite a few of which I don't agree with), time and effort would be better spent on reviewing code and using features before releases e.g. to avoid situations like the FFI api being difficult to use. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
