`trace`/`debug`/`info`/`warn`/`error` with marker deprecated though alternative is ambigious

[jensbaitingerbosch]

I will explain this bug with info(...), the same issue with debug, warn etc.

KLogger.info(Marker, ()-> Any?) is marked as deprecated withe the replacement info(null, marker, msg)

The issue is, that using this replacement is ambiguous causing the following compiler error:

Overload resolution ambiguity between candidates:
fun info(marker: Marker?, t: Throwable?, msg: () -> Any?): Unit
fun info(marker: Marker?, msg: String?, arg: Any?): Unit

Only calling the function like this log.info(marker, throwable=null, msg) satisfies the compiler. Which makes the call more complex (even with log.info(marker, null, msg) the null looks unnecessary.

Suggestion: undeprecate the function KLogger.info(Marker, ()-> Any?).

[github-actions]

Thank you for reporting an issue. See the wiki for documentation and slack for questions.

[oshai]

I understand the issue. The thing is that too many options for parameters also makes the api cumbersome and confusing.

Another option is using:

logger.atInfo(marker) {
  message = msg
}

[xjw580]

I understand the issue. The thing is that too many options for parameters also makes the api cumbersome and confusing.

Another option is using:

logger.atInfo(marker) {
  message = msg
}

Assigning a value to the message field is very cumbersome.