SLF4J / SLF4J-371 [Resolved] Support the lambda expression in the Logger ==============================
Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-371 ============================== 1 comment ------------------------------ Eric Kolotyluk on 27/Dec/21 6:38 PM > Just to make things clear: the last listing won't work either Fair enough {code:java} Supplier task = () -> {System.out.println("task evaluated"); return "called";}; {code} but I am not sure why you are missing/ignoring my point? {code:java} logger1.atDebug().addArgument(() -> "called").log("Lazy logging {}"); {code} is just uglier than {code:java} logger2.debug("Lazy logging {}", () -> "called"); {code} I can only conclude that you are using deliberately pointing at stupid and insignificant errors in my examples as some ad hominem argument to score points, to deflect, to minimize, to advocate for Fluent, to promote political opinion instead of technical opinion? What is your point? _I joined this conversation to simply advocate for adding 'nice' lambda support in SLF4J, nothing more. Eventually I learned that SLF4J 2.0 has some minimal support, but at the cost have 'having' to learn/use Fluent. Eventually I learned there is a facade for the SLF4J facade that does exactly what I was advocating for in the the first place._ I do not understand why my comments have been met with so much hostility and perversion by trolls posing as professionals. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59) _______________________________________________ slf4j-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-dev
