There are ambiguities from time to time. But as soon as they appear, the compiler is so nice to tell me about them. There is a compile error that is usually very easy to fix. Unlike for example C++, the c++ linker is used to throw stuff away that have been defined several times. That has to do with the fact that in header files types have to be defined a lot, and the linker is forced to throw a lot of stuff away, sometimes c++ silently throws stuff away that should have better been reported. And then you have a very very horrible job in finding the result. So just because name collisions are something very horrible in c++, it doesn't mean that they cause the same kind of problem in Nim.
Not knowing where a method comes from could be a problem when your only tool to read and write the sourcecode is notepad. But generally development tools can tell you where a function comes from in case you don't know it. If this is constantly a problem, then there might be a problem in the naming conventions in the used libraries.
