[
https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383257#comment-16383257
]
Raman Gupta commented on LOG4J2-1705:
-------------------------------------
I didn't see [[email protected]]'s message until just now... for the Kotlin API
I would prefer non-nullable `Marker` as per [~jvz]'s initial comments. In my
experience, marker's tend to be relatively simple, usually constant, values. If
the marker is instead the result of calculations, then the user is already
implementing extra logic anyway. In that case, Kotlin's elvis operator makes it
easy to add a fallback marker value.
> Kotlin wrapper for Log4j 2 API
> ------------------------------
>
> Key: LOG4J2-1705
> URL: https://issues.apache.org/jira/browse/LOG4J2-1705
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Reporter: Raman Gupta
> Priority: Major
>
> Similar to LOG4J2-1181 for Scala, provide a Kotlin wrapper for the Log4j 2
> API that makes use of Kotlin features like delegates and string interpolation.
> If there is interest in this, I'd like to contribute a patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
