find-non-lambda-logs

Inefficient Kotlin Android logging occurs when Log.d, Log.i, Log.w, and Log.e calls use direct string interpolation instead of lambda overloads, causing unnecessary string allocations even when debug logs are filtered out during runtime.

You can audit Log.d, Log.i, Log.w, and Log.e calls by performing pattern-based Kotlin source inspection to identify string interpolation misuse, throwable exceptions, and direct android.util.Log leakage bypassing shared wrappers.

Check for string interpolation misuse in Log.d, Log.i, Log.w, and Log.e calls when reviewing an Android codebase after adding new logs or migrating logging infrastructure to locate and optimize allocation-heavy logging statements.

Yes, the logging audit detects direct android.util.Log usage that bypasses shared logging wrappers and release filtering strategies by inspecting Kotlin source code patterns for leakage and interpolation misuse.

Yes, you can use this logging audit for Kotlin Android code migrations to locate Log.d, Log.i, Log.w, and Log.e statements requiring lambda conversions and throwable exception handling during logging infrastructure updates.

Pattern-based source inspection for log optimization is limited to detecting non-lambda Log statements with string interpolation in Kotlin Android code, requiring source access and focusing on static interpolation misuse rather than runtime performance profiling.