Re: Another Koenig lookup thread, yes, kill me now

Now, I don't want to start a flame thread, and I apologize for
bringing this up. However, I do have a couple things I would like
clarified. To start, here's one of the well known problems with Koenig
lookup.

// **** main problem
namespace A
{ class foo {};
     template <typename T> void helper (T) {}
}
namespace B
{ template <typename T> void helper(T ) {}

     template <typename T>
     class set
     {
     public:
         set()
         { T tmp;
             helper(tmp);
         }
     };
}
int main() { B::set<A::foo *> s; }
// ****

I actually had this happen to me in production code. I ended up
changing
     int main() { B::set<A::foo *> s; }
to
     int main() { B::set<void *> s; }
to get around Koenig lookup, and static_cast'ing on each use. I really
disliked how I had to abandon type safety. I was in a no win
situation. namespace B was the compiler's STL, and namespace A was a
company-wide header which was not going to change.