Avoid usage of low-level logging call Log.println?

[G00fY2]

If the Log level is != ASSERT the library uses the low-level logging method Log.println(priority, tag, part).

I know that this part is borrowed from Timber, but I wonder what the benefit of this is, over using the corresponding higher level log methods (Log.v, Log.d ...)? Because from my understanding (have not tested it) this will prevent R8 from removing the logging calls with this recommended and commonly used proguard rule:

-assumenosideeffects class android.util.Log {
    public static boolean isLoggable(java.lang.String, int);
    public static int v(...);
    public static int i(...);
    public static int w(...);
    public static int d(...);
    public static int e(...);
}

I would suggest to change the logToLogcat function to this:

private fun logToLogcat(
  priority: LogPriority,
  tag: String,
  part: String
  ) {
    when (priority) {
      LogPriority.VERBOSE -> Log.v(tag, part)
      LogPriority.DEBUG -> Log.d(tag, part)
      LogPriority.INFO -> Log.i(tag, part)
      LogPriority.WARN -> Log.w(tag, part)
      LogPriority.ERROR -> Log.e(tag, part)
      LogPriority.ASSERT -> Log.wtf(tag, part)
    }
}

Any opinions?