earthquake changes of std.regexp to come

[Ellery Newcomer]

Andrei Alexandrescu wrote:
> Leandro Lucarella wrote:
>> Andrei Alexandrescu, el 17 de febrero a las 13:56 me escribiste:
>>>> Btw, I've got no problems with you breaking the API of 2.0 either.
>>>> Though you might consider moving the current implementation to
>>>> std.deprecated.regex and leaving it there for a year with a
>>>> pragma(msg, "This module is deprecated").
>>>> That way making a quick fix to broken code is just a matter of
>>>> inserting ".deprecated" into your import statements.
>>>
>>> I was thinking of moving older stuff to etc, is that ok?
>>
>> What's the rationale for "etc"? Why not "deprecated", o something shorter
>> like "old", or "d1" (this last one could be good for future deprecated
>> libraries, like when D3 is available there probably be a "d2" too).
>>
> 
> In the words of George Costanza: "Because it's there!"
> 
> Andrei

Shouldn't that be George Mallory?