tracing: prepare to release 0.1.16 #789
Merged
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.
Added
#[instrument]
(attributes: support arbitrary field expressions #672)#[instrument]
now emits a compiler warning whenignoring unrecognized input (attributes: support arbitrary field expressions #672, attributes: downgrade unrecognized input errors to warnings #786)
tracing
in async code (docs: better docs on async usage; fancy warning formatting, etc #769)Changed
tracing-core
dependency to 0.1.11Fixed
longer compilation times (tracing: attempt to monomorphize is_enabled call #787)
log
orlog-always
featuresare enabled (tracing: fix warnings with
log
/log-always
features #753)tracing-core/std
feature is enabled buttracing/std
is not (Adjust Once to not violate feature additivity principle #760)Thanks to @nagisa, and everyone who contributed to the new
tracing-core
and
tracing-attributes
versions, for contributing to this release!