This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Aug 2005 14:12:02 -0000
- Subject: [Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- References: <20040610143911.15910.king.benjamin@mh-hannover.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bangerth at dealii dot org 2005-08-09 14:11 -------
I think we should all recuse ourselves from this discussion, since we just
keep iterating our same old positions:
Yongwei believes that this is a defect in the standard and that gcc should
not follow the standard in this respect.
Gaby and I believe that gcc should follow the standard, and probably both
believe that the standard does not have a defect in this respect. We believe
that changing the standard would require a massive change in the language,
since it would either a) require the introduction of concepts (so that
std::distance can only be called with arguments that match the concept
of an iterator; same for all other similar functions), or b) abandoning
argument dependent (Koenig) name lookup. Neither sounds like an appealing
idea. We believe that users can work around this perceived problem by
simply calling
::distance (arg1, arg2)
to get to their own implementation, not the one in std::
Since we can't seem to find an agreement, let's just leave it at that.
W.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910