Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109863
To: PHP internals <internals@lists.php.net>
References: <CANOvohpz5OzHZSxdABncBXRQfeF-XnKqpK8BBDQ8OeT+jBL96w@mail.gmail.com>
 <5ea5e72d.1c69fb81.ecd6b.8d05SMTPIN_ADDED_MISSING@mx.google.com>
 <CALKiJKpjwrdhnQT35myRRC-Sx-kFLzNQ6=a7J-_yEyzFm+2XVA@mail.gmail.com>
 <F519C26E-E65E-46E5-9B70-74259310E774@newclarity.net>
Message-ID: <29bd50e0-51d5-e8a1-10c4-bf89d42124c3@gmail.com>
Date: Mon, 27 Apr 2020 23:05:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <F519C26E-E65E-46E5-9B70-74259310E774@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] PHP Namespace Policy
From: rowan.collins@gmail.com (Rowan Tommins)

On 27/04/2020 22:40, Mike Schinkel wrote:
> How about a simply policy:  Newer things go in, older ones stay out?
>
> Check the docs to see which is which if you are unsure, or just let your IDE auto-complete for you.


So you'd be happy with PHP\str_contains and \str_replace next to each 
other indefinitely? Or, more in line with your proposal, a hypothetical 
PHP\Iterators\FractallyAwesomeIterator next to \InifiniteIterator, 
\LimitIterator, etc? Or did you have some stronger definition of "newer 
things" in mind?

I don't really see what such an arbitrary split would gain us, other 
than a lot of confusion. Importantly, it wouldn't be following the lead 
of the other languages and frameworks you mentioned, which was the 
specific point I was responding to.

Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]