You should define them in the library namespace.
The compiler will find them anyway through argument dependant lookup.
No need to pollute the global namespace.
More Related Contents:
- How to properly overload the
- Where should non-member operator overloads be placed?
- Does my overload of operator
- Accessing members in same namespace in C++ [closed]
- Unnamed/anonymous namespaces vs. static functions
- Why must the copy assignment operator return a reference/const reference?
- virtual assignment operator C++
- How do you properly use namespaces in C++?
- When to Overload the Comma Operator?
- In C++, what is a “namespace alias”?
- What are the pitfalls of ADL?
- Making operator
- Global scope vs global namespace
- Why is “using namespace X;” not allowed at class/struct level?
- scope of using declaration within a namespace
- Operator overloading outside class [duplicate]
- operator= and functions that are not inherited in C++?
- difference between global operator and member operator
- Const and Non-Const Operator Overloading
- Overloading assignment operator in C++
- C++ namespaces advice
- Uses for anonymous namespaces in header files
- Why can’t I forward-declare a class in a namespace using double colons?
- error C2065: ‘cout’ : undeclared identifier
- How could comma separated initialization such as in Eigen be possibly implemented in C++?
- Why does C++ parameter scope affect function lookup within a namespace?
- Overloading operator
- What is the use of “using namespace std”? [duplicate]
- extern “C” linkage inside C++ namespace?
- How can it be useful to overload the “function call” operator?