Getting the const-correctness of Object sorted once and for all

deadalnix deadalnix at gmail.com
Mon May 14 12:20:17 PDT 2012


Le 14/05/2012 21:04, Mehrdad a écrit :
> On Monday, 14 May 2012 at 18:52:06 UTC, deadalnix wrote:
>> The only reason I'd see a toSting function as non pure or non const is
>> memoize. It can be tackled with lib support in phobos.
>> What are other uses cases ?
>
> Not necessarily 'memoization' -- you could be instead querying
> another object for this information, which may not be const.
> (Say, a network connection.)

I'd argue that hiding such an operation in toString or similar stuff is 
what you want to avoid.


More information about the Digitalmars-d mailing list