Fun with range deprecations

[Meta via Digitalmars-d]

On Monday, 11 August 2014 at 23:45:27 UTC, H. S. Teoh via 
Digitalmars-d wrote:
> On Tue, Aug 12, 2014 at 02:38:24AM +0300, ketmar via 
> Digitalmars-d wrote:
>> On Mon, 11 Aug 2014 15:57:50 -0700
>> "H. S. Teoh via Digitalmars-d" <digitalmars-d at puremagic.com> 
>> wrote:
>> 
>> seems that such deprecations hits even rdmd: trying to compile 
>> it now
>> spits two warnings about "std.algorithm.splitter cannot be 
>> iterated
>> backwards".
>
> Incidentally, it was while compiling the latest rdmd repo that 
> I first
> noticed this issue. ;-)
>
>
> T

What about modifying is(typeof(...)) to return false for 
deprecated symbols?

The thing is that this will break code, and it will continue to 
break code in the future if somebody deprecates a symbol which is 
used in an is(typeof(...)) expression. That makes it a lot harder 
for us to deprecate anything. There doesn't seem like any *good* 
solution to this problem.