home bbs files messages ]

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 33,308 of 33,346   
   James K. Lowden to Marc   
   Re: transform, make_pair, and rvalues   
   14 Apr 14 22:31:39   
   
   From: jklowden@speakeasy.net   
      
   On Sun, 13 Apr 2014 13:52:16 CST   
   Marc  wrote:   
      
   > > transform( a.begin(), a.end(), b.begin(), inserter(c, c.begin()),   
   > > 	   make_pair );   
   >   
   > Never specify the parameters for make_pair. I have never seen code   
   > where that was a good idea.   
   >   
   > > The compilation error from VC11 said it couldn't convert parameter   
   > > 2 of make_pair from uint64_t&& to uint64_t.   Bug or feature?   
   >   
   > Feature. Those parameters are meant to be deduced by the compiler.   
      
   Was that the intention?  I don't have a compiler that will deduce   
   template parameters for a supplied function to std::transform.  I admit   
   I don't know *why* I don't have such a compiler, because ISTM all the   
   necessary information is present and accounted for.   
      
   So ... can we agree on bug instead?  Because implementations are   
   falling down on the job?  Or bug, because the language defintion   
   prevents them from doing so, and forces me to supply parameters that are   
   incompatible across versions of the language?   
      
   Feature I'm having trouble seeing.   
      
   --jkl   
      
      
   --   
         [ 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