GitHub user rocketraman closed the discussion with a comment: No use of `inline` in `log4j-api-kotlin`?
@mcmacker4 There was an attempt to make these functions inline some time ago, however it caused issues with losing caller location information. See https://github.com/apache/logging-log4j-kotlin/pull/7 for the discussion. At the moment the main solution being considered is to move to a Kotlin compiler-plugin based approach, which should allow us to solve this problem as well as provide various other capabilities as well, such as https://github.com/apache/logging-log4j-kotlin/issues/139. I'll close this discussion here as I believe this answers the concern and explains the reason why these functions are not currently inline, as well as explains to some extent the roadmap. Feel free to raise more specific issues or PRs in the logging-log4j-kotlin repo. GitHub link: https://github.com/apache/logging-log4j2/discussions/4146#discussioncomment-17440026 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
