performance problem: logger.*(lambda) are not inlined about kotlin-logging HOT 2 CLOSED

Thanks for your report. It was like that before, the main problem is with LocationAwareLogger - inlined methods cause it to show incorrect line numbers on the log messages. I hope in the future labmda expresssion will be optimized to create such overhead. let me know what you think about that.

from kotlin-logging.

If anyone is interested, I combined code from this and Anko to make a really trimmed down logger that:

• Drops location-aware support and inlines everything
• Drops the slf4j dependency and just uses android.util.Log
• Renames method and object names so you call it the exact same way you'd call android.util.Log.
• Adds an optional enabled: Boolean param to the Logger class (the one that your companion object will extend) to disable/enable logging on a class-by-class basis. If omitted it'll just default to whatever's defined in the logging file.
• Destroys several of the nice abstractions and crams everything into one file, because I'm a terrible person.
• Drops the tests because I'm lazy. Planning to re-add at some point.

Currently living here, might split it out into a separate lib at some point.

I also have not tested to make sure I didn't screw up and butcher the performance.

from kotlin-logging.