From: daniel.kruegler@googlemail.com   
      
   On 2011-08-13 00:40, Marc wrote:   
   > Daniel Krügler  wrote:   
   >   
   >> I withdraw this remark: After sending this reply, I found a reasonable   
   >> answer myself: In contrast to std::async or std::thread, there does not   
   >> exist a single-call guarantee of the result of a std::bind expression.   
   >> But if we would specify std::bind such that every call expression of the   
   >> result object would potentially move some of the bound arguments (or the   
   >> functor for that matter), this would mean that only a single call would   
   >> be guaranteed to be well-defined. Therefore I think that the current   
   >> intention of std::bind makes very much sense.   
   >   
   > So do you think there should be a std::bind_unique for single-call   
   > cases (are there other functions that would benefit from a   
   > move-enabled variant?)? Or are the uses rare enough that they should   
   > handle things manually?   
      
   Personally I have not found yet a reasonable amount of examples where   
   std::bind_single would satisfy the effort of standardizing it. Opinions   
   may differ, but in this case I would suggest to make a proposal paper   
   for such an addition for another standard revision, if indeed wanted.   
      
   HTH & Greetings from Bremen,   
      
   Daniel Krügler   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)