Improve performance of Tracer.invoke() function #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve performance of
Tracer.invoke()
:Changes:
Tracer.invoke()
function.TraceEvent
object if there are no event consumers. This saves us from performing an expensiveLocalDateTime.now()
call.createLogMessage()
functions. Only useStringBuilder
functions.toStringRegistry
to useitem::javaClass.name
as key, and useitem::class.toString()
only as fallback.item.javaClass.getMethod("toString").declaringClass
inconvertToStringUsingRegistry()
: theitem.toString()
function ofAny
will anyway print the name of the class.extensions
andtraceevents
modules): no unit test for these modules was being run anymore, after the 1.8.2 update.IfExtensionsTest
unit tests: these tests were broken by mockk 1.13.4 (due to Broken spying on functions mockk/mockk#1033).