Steve Ebersole, I understand and I agree with changing the logging level and adding the function to the message. What I am not sure about is the suggestion for throwing an exception when the supplied number of arguments are outside of [min,max]. Perhaps the reason why we didn't previously is we couldn't support a range-based argument check properly, hence why we merely logged the warning. I'm just suggesting we consider all use cases before adding the exception-case.