Eliza Weismanandcsmoe 847fb59b17 trace-core: Introduce callsite classification in metadata (#1046) ...

## Motivation

To ease the implementation of `Subscriber::register_callsite`, a field
should be added to `Metadata` to indicate if this callsite is an event or
a span.

## Solution

A new struct, `Kind`, is added to the `metadata` module in
`tokio-trace-core`, and a `Kind` field is added to the `Metadata`
struct. Macros which construct `metadata` now require a `Kind`.

`Kind` is represented as a struct with a private inner enum to allow new
`Kind`s to be added without breaking changes. However, the _addition_ of
the kind field _is_ a breaking change. While this could be done in a
backward-compatible way, it would permit the construction of metadata
with unknown kinds, and since the next `tokio-trace-core` release will
be a breaking change, I opted to make the breaking change instead.

New API tests for the `callsite!` and `metadata!` macros have been added
to guard against future API breakage.

Fixes: #986
Closes: #1008

Co-Authored-By: csmoe <[email protected]>

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

..

event.rs

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

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

field.rs

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

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

metadata.rs

Introduce tokio-trace (#827)

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

mod.rs

trace: Allow specifying a new span's parent (#923)

2019-03-01 11:29:11 -08:00

span.rs

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

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

subscriber.rs

trace-core: Require span IDs to be > 0 (#973)

2019-03-11 16:18:40 -07:00