Shortcut logging for errors about log15 HOT 1 CLOSED

I sympathize with the redundancy, but I think this kind of special casing of the API would make it more confusing. The use of an even number of arguments for alternating key-value pairs is already pushing the limits of acceptability, adding special cases to it would add complexity for both the library and for developers puzzling over the exceptional behavior, which to my mind doesn't justify shortcutting a few extra characters in the logging code. Finally, it's easy enough for someone to create their own new logger object wrapper with an additional method that implements this behavior.

from log15.