Function naming is unnecessarily confusing

[joshuaehill]

There are instances in the source base where the same function name is used to denote different (unrelated) functions. In some cases, this is resolved by polymorphism (as the parameters are clearly different), and in others this is resolved through including different portions of the source base in compilation.

In both cases, this is bad practice. Polymorphism provides for a way of labeling the same "conceptual" operation in the same way across different uses, but this doesn't appear to be what is going on here. For the case where unrelated functions just happen to be named the same way, that's unnecessarily confusing.