Log.d in Android java source

Why do we use Log.d within the Android sources without a if (BuildConfig.DEBUG) check? Log.d has an impact on performance, so it should be minimised in release builds.

Currently every Log.d call is written into the logcat, even in the release build. In the C++ code we can use CCLOG, which will be truncated in the release build, but not in the Java code.

Should I create a feature request/pull request for that?

1 Like