mirror of https://github.com/tokio-rs/tokio.git synced 2026-08-27 00:00:12 +02:00

Files

T

Eliza Weisman d4adeeef2f trace: Remove the AsId trait (#1145 )

While we're making breaking changes to `tokio-trace`, it would be good
to get rid of the `AsId` trait. The goal of span functions that are
generic over `Span`/`Id` can be achieved without the unnecessary
complexity of defining a new trait. This would also make the API added
to `tokio_trace_core::Event` in #1109 more consistent with the
`tokio-trace::Span` API.

This branch removes `AsId` from `tokio-trace` and replaces its uses with
`impl Into<Option<Id>>` and `impl Into<Option<&'a Id>>`. While `AsRef`
might be more semantically correct for the borrowed-`Id` conversion, its
signature doesn't permit conversion into an `Option`. Implementations of
`Into<Option<Id>>` and `Into<Option<&'a Id>>` have been added for 
`tokio_trace::Span`.

This is _technically_ a breaking API change, as it changes function
signatures. However, the existing macro syntax still works as-is, and
the tests which pass `&Id`, `&Span`, and `&Option<Id>` to the span
macros all still compile after this change.

Closes #1143

Signed-off-by: Eliza Weisman <[email protected]>

2019-06-13 12:53:08 -07:00

src

trace: Remove the AsId trait (#1145 )

2019-06-13 12:53:08 -07:00

tests

trace-core: Introduce callsite classification in metadata (#1046 )

2019-04-11 11:56:42 -07:00

Cargo.toml

chore: remember to remove path deps on release (#1057 )

2019-04-24 10:42:39 -07:00

CHANGELOG.md

trace-core: prepare for 0.2 release (#1047 )

2019-04-21 10:20:28 -07:00

LICENSE

Introduce tokio-trace (#827 )

2019-02-19 12:15:01 -08:00

README.md

trace-core: prepare for 0.2 release (#1047 )

2019-04-21 10:20:28 -07:00

README.md

tokio-trace-core

Core primitives for tokio-trace.

Documentation

Overview

tokio-trace is a framework for instrumenting Rust programs to collect structured, event-based diagnostic information. This crate defines the core primitives of tokio-trace.

The crate provides:

Span identifies a span within the execution of a program.
Event represents a single event within a trace.
Subscriber, the trait implemented to collect trace data.
Metadata and Callsite provide information describing Spans.
Field, FieldSet, Value, and ValueSet represent the structured data attached to a Span.
Dispatch allows span events to be dispatched to Subscribers.

In addition, it defines the global callsite registry and per-thread current dispatcher which other components of the tracing system rely on.

Application authors will typically not use this crate directly. Instead, they will use the tokio-trace crate, which provides a much more fully-featured API. However, this crate's API will change very infrequently, so it may be used when dependencies must be very stable.

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.