Or use a good IDE which would have something like "right click -> jump to declaration" and it will show you what/where the function is implemented. Or at least that's what I do to keep up my productivity instead of wondering at the marvels of overloading / namespaces that export same function names.
The complexity of the language makes it hard to do even for state-of-the-art IDEs. I have had up to date versions of CLion suggest a dozen potential declarations in some hairy codebases...
The point of the article is not to manually resolve all function calls. Understanding the algorithm allows you to see why a compiler sometimes doesn't choose the function you want and fix it.
Huh... So your saying "right click -> jump to declaration" uses the compiler to resolve all the candidate functions to determine the function that would of been chosen at compile time? ..and then take you to that function? I thought it just took you to the 1st occurrence of the function it found. If so, that's interesting.
Really depends on your IDE. As an example, Visual Studio ships Microsoft's CPP compiler (MSVC [0]), but uses a completely different compiler frontend (namely EDG [1]) for IntelliSense.
In a way, it does use a compiler to resolve the candidate functions, but it doesn't go through all the compilation stages. And it's not even the same compiler as when you hit compile :)
