... darkrealms ...

Forums before death by AOL, social media and spammers... "We can't have nice things"

comp.lang.c++.moderated

Moderated discussion of C++ superhackery

33,346 messages

[ << oldest | < older | list | newer > | newest >> ]

Message 32,646 of 33,346

Gene Bushuyev to All

Re: lambda objects not assignable

13 Nov 12 11:51:22

   From: publicfilter@gbresearch.com   
      
   On Thursday, November 8, 2012 10:02:07 AM UTC-8, Vladimir Petrović wrote:   
   >   
   > The standard explicitly states that operator= is deleted from the   
   >   
   > lambda object's type. What is the rationale for such decision ?   
      
   Maybe I'm missing something here, but apart from self-assignment   
   there isn't any other object of the same closure type, so what would   
   be the use of copy assignment?   
      
      
   --   
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)

[ << oldest | < older | list | newer > | newest >> ]