Logic definitions in refreshed library content specify a libraryName and a name, but the name for function definitions does not include the signature, so overloads result in duplicate libraryName/name combinations, so there is no way for template content to uniquely identify function overloads.
This leads to duplicate anchors and duplicate potential targets when generating liquid templates.
See the MultirateExample measure in the Quality Measure IG for an example.
The solution is name-mangling the signature, should be easy enough to construct, and I believe we are already doing something similar to avoid collisions while de-duplicating data requirements.