The introduction of lambdas was made in conjunction with another even more profound change, namely the fluent-api.
The fluent api makes the introduction of changes in the Logger class both cheaper and avoids creating a combinatorial explosion. It took time to commit to this change as once released, such client visible changes to the API cannot be taken back.
On 12/08/2019 17:04, anandsaw wrote:
Hi Ceki, Thank you again for the response and pointing us to version 2.0.0. We appear to have not looked at that one (as it was publicly released after our initial manual analysis). This would imply that in our investigation SLF4J is one of the APIs that has made a change. Just so that we can document this correctly, could you please elaborate on why this change was made? And what the process was? And why this has taken time since the initial issue? Thank you again for being responsive, this quite the help for us! Regards, Anand Sawant. -- Sent from: http://slf4j.42922.n3.nabble.com/slf4j-dev-f41812.html _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev
