-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom format for Trace #20
Comments
SokolovaMaria
added a commit
that referenced
this issue
Dec 11, 2019
SokolovaMaria
added a commit
that referenced
this issue
Jan 19, 2020
elizarov
pushed a commit
that referenced
this issue
Mar 5, 2020
elizarov
pushed a commit
that referenced
this issue
Mar 31, 2020
* Avoid trace allocations for default non-traced atomics. Trace format changes. * Supports naming traces with trace.name("foo"). * System property 'kotlinx.atomicfu.trace.thread' to include thread name into the default format on JVM. * Improved Trace.toString implementation. * A separate type for TraceFormat: - Avoids boxing of integer index. - Makes it a bit less convenient to use (but Ok, since it is not a common feature). - Its full removal from bytecode is not supported now (might be Ok, TBD). WIP: JS transfromer needs to be fixed. Fixes #20
elizarov
pushed a commit
that referenced
this issue
Oct 9, 2020
* Avoid trace allocations for default non-traced atomics. Trace format changes. * Supports naming traces with trace.name("foo"). * System property 'kotlinx.atomicfu.trace.thread' to include thread name into the default format on JVM. * Improved Trace.toString implementation. * A separate type for TraceFormat: - Avoids boxing of integer index. - Makes it a bit less convenient to use (but Ok, since it is not a common feature). - Its full removal from bytecode is not supported now (might be Ok, TBD). WIP: JS transfromer needs to be fixed. Fixes #20
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a potential future enhancement.
Support custom tracing format using the following DSL:
The text was updated successfully, but these errors were encountered: