Skip to content
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

tracing-core: add documentation on DefaultCallsite #2149

Merged
merged 1 commit into from
Jun 6, 2022

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Jun 6, 2022

This adds a small note on the use of DefaultCallsite to the
tracing-core docs. I wanted to take care of this before publishing a
new tracing-core release.

This adds a small note on the use of `DefaultCallsite` to the
`tracing-core` docs. I wanted to take care of this before publishing a
new `tracing-core` release.
@hawkw hawkw requested a review from davidbarsky June 6, 2022 17:09
@hawkw hawkw requested a review from a team as a code owner June 6, 2022 17:09
@hawkw hawkw merged commit a29fbc6 into v0.1.x Jun 6, 2022
@hawkw hawkw deleted the eliza/default-callsite-docs branch June 6, 2022 18:11
hawkw added a commit that referenced this pull request Jun 7, 2022
# 0.1.27 (June 7, 2022)

This release of `tracing-core` introduces a new `DefaultCallsite` type,
which can be used by instrumentation crates rather than implementing
their own callsite types. Using `DefaultCallsite` may offer reduced
overhead from callsite registration.

### Added

- `DefaultCallsite`, a pre-written `Callsite` implementation for use in
  instrumentation crates ([#2083])
- `ValueSet::len` and `Record::len` methods returning the number of
  fields in a `ValueSet` or `Record` ([#2152])

### Changed

- Replaced `lazy_static` dependency with `once_cell` ([#2147])

### Documented

- Added documentation to the `callsite` module ([#2088], [#2149])

Thanks to new contributors @jamesmunns and @james7132 for contributing
to this release!

[#2083]: #2083
[#2152]: #2152
[#2147]: #2147
[#2088]: #2088
[#2149]: #2149
hawkw added a commit that referenced this pull request Jun 7, 2022
# 0.1.27 (June 7, 2022)

This release of `tracing-core` introduces a new `DefaultCallsite` type,
which can be used by instrumentation crates rather than implementing
their own callsite types. Using `DefaultCallsite` may offer reduced
overhead from callsite registration.

### Added

- `DefaultCallsite`, a pre-written `Callsite` implementation for use in
  instrumentation crates ([#2083])
- `ValueSet::len` and `Record::len` methods returning the number of
  fields in a `ValueSet` or `Record` ([#2152])

### Changed

- Replaced `lazy_static` dependency with `once_cell` ([#2147])

### Documented

- Added documentation to the `callsite` module ([#2088], [#2149])

Thanks to new contributors @jamesmunns and @james7132 for contributing
to this release!

[#2083]: #2083
[#2152]: #2152
[#2147]: #2147
[#2088]: #2088
[#2149]: #2149
kaffarell pushed a commit to kaffarell/tracing that referenced this pull request May 22, 2024
# 0.1.27 (June 7, 2022)

This release of `tracing-core` introduces a new `DefaultCallsite` type,
which can be used by instrumentation crates rather than implementing
their own callsite types. Using `DefaultCallsite` may offer reduced
overhead from callsite registration.

### Added

- `DefaultCallsite`, a pre-written `Callsite` implementation for use in
  instrumentation crates ([tokio-rs#2083])
- `ValueSet::len` and `Record::len` methods returning the number of
  fields in a `ValueSet` or `Record` ([tokio-rs#2152])

### Changed

- Replaced `lazy_static` dependency with `once_cell` ([tokio-rs#2147])

### Documented

- Added documentation to the `callsite` module ([tokio-rs#2088], [tokio-rs#2149])

Thanks to new contributors @jamesmunns and @james7132 for contributing
to this release!

[tokio-rs#2083]: tokio-rs#2083
[tokio-rs#2152]: tokio-rs#2152
[tokio-rs#2147]: tokio-rs#2147
[tokio-rs#2088]: tokio-rs#2088
[tokio-rs#2149]: tokio-rs#2149
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant