Revised RFC on range design for D2

[Sergey Gromov]

Sat, 27 Sep 2008 09:13:54 -0500,
Andrei Alexandrescu wrote:
> If you want to discuss language design mistakes, why don't you discuss a 
> real mistake - the infamous "lazy"? Having a storage class change the 
> way a type is used - now that's the perfect example of the tail wagging 
> the dog. Ambiguity, confusion, non-scalability, and sheer nonsense - you 
> can have it all with lazy. Lazy should be either fixed or honorably 
> discharged pronto.

Because I use class and struct fields, I use properties, I use 
functions, delegates, aliased functions, vararg templates and 
conditional compilation---but I never had need for lazy yet.