This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)


------- Additional Comments From bangerth at dealii dot org  2005-08-06 17:18 -------
I agree with Gaby: the standard pretty unambiguously lists the signature of 
std::distance, and the name lookup rules say that it needs to be found. What 
leeway do we have in rejecting it anyway and picking anything else? The fact 
that you want another function to be found is not a normative clause that 
can be derived from the standard. 
 
However, as has been proposed before: the correct course of action is to  
lobby the standards committee to introduce some notion of "concept" and  
specify that the std::distance function shall only be used if its arguments 
conform to a certain concept. This has been done in the past using means 
like boost::enable_if, but the standard doesn't use such things at present 
so I don't see how we can modify libstdc++ in a way that conforms with 
the present standard. 
 
I therefore close this PR as suggested by Gaby. 
 
W. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]