Support logger.error(message: String, t:Throwable)

[analytically]

For easier migration from eg. Scala-Logging or SLF4J.

[sarahgerweck]

This is an interesting suggestion. I'm not in love with having two ways of doing the same thing, so I'll have to give it some thought.

One Idea I have would be to have an extra org.log4s.compat._ interface that you can import to get access to compatibility APIs like this. I assume that would satisfy your needs well enough? I think I could make that work without adding any runtime overhead, and it would provide a way to support lots of legacy interfaces, like the template-based SLF4J interfaces in addition to the Throwable logger.

[rossabaker]

+1 to the compat interface. That would greatly ease adoption on legacy code without polluting "The Log4s Way."

[sarahgerweck]

All right, a compat package with some façades seems to be the way to go here. It will be just another import you can toss into your code to get additional interfaces.

I've also been planning to add support for SLF4J's Markers, so I'll probably do both of these in one shot. (Markers are the last missing feature that might change the preferred API for standard logging stuff, so it'll be a good thing to nail down before building the compatibility layers.)

I'll probably have time to get to this enhancement by the end of the year.

[larsrh]

Is marker support still planned?

[sarahgerweck]

@larsrh I haven't heard too much interest in markers, but if you have a use case then I will take another look at how to add these in. I don't think it's difficult, I just need to consider what the API should look like and write the macros.

[larsrh]

I don't need it right away, it's just something somewhere on my to-do-list. The use case is to support different "log sections" of a system, i.e., I want to declare that "trees" and "types" should be logged in my application.