Why callers should explicitly document storage classes

[Timon Gehr]

On 08/14/2011 10:00 PM, Vladimir Panteleev wrote:
> On Sun, 14 Aug 2011 22:48:18 +0300, Timon Gehr <timon.gehr at gmx.ch> wrote:
>
>> requiring lazy before lazy arguments basically destroys the reason for
>> lazy being in the language:
>>
>> int foo(lazy 2*3);
>>
>> is not better than
>>
>> int foo({return 2*3});
>
> What about requiring "lazy" only for non-pure delegates?
>

Actually I would rather require lazy arguments to be pure, so that they 
can be guaranteed to be executed at most once.