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,650 of 33,346    |
|    Zhihao Yuan to All    |
|    Re: lambda objects not assignable    |
|    14 Nov 12 17:03:56    |
   
   From: lichray@googlemail.com   
      
   { Please limit your text to fit within 80 columns, preferably around 70,   
    so that readers don't have to scroll horizontally to read each line.   
    In addition, please avoid double-spacing the quoted material.   
    This article has been reformatted manually by the moderator. -mod }   
      
   > 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?   
      
   I think this is the main reason -- lambda types are identical to each   
   other, and both the lambda and their type are unnamed. Assignment does   
   not work with different types. And self-assignment is impossible,   
   because lambda is a prvalue.   
      
      
   --   
    [ 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 >>   ]
(c) 1994, bbs@darkrealms.ca