Fallback 'catch-all' template functions

[Ethan Watson via Digitalmars-d]

On Thursday, 1 September 2016 at 11:01:28 UTC, Dominikus Dittes 
Scherkl wrote:
> Ok, that may be fine, until you reach the point with the 
> fallback version: if after that point someone "drops in" a new 
> version, he silently changes the behavior of the function, 
> because he "steals" some type which used to use the fallback 
> version.

I don't see how that can be considered anything other than 
"expected behaviour" and thus ensure your design takes this in to 
account. If you give your user the keys to the kingdom, you need 
to expect them to use it.