macro to place logger in the companion

Having a val log in every instance is extremely expensive… more so for lazy vals.

It would be much more efficient if the val lived on the companion and the log were a def that delegated.

To pull this off, one would have to implement this as a macro or compiler plugin.

Until then, I see no real benefit of using this library over say, akka’s Slf4jLogging trait, which already exists on most classpaths.

[hseeberger]

I see. But that’s indeed out of scope, because Scala Logging will only use blackbox macros.

[hseeberger]

@fommil you don’t have to mix the StrictLogging (or LazyLogging) trait into your classes. If you want, you can simply create a Logger “manually” in a companion object and just use it from your companion classes.

Nevertheless I don’t think that mixing StrictLogging (or LazyLogging) into your classes creates too much overhead, because the logging framework will only create one logger instance per class name.