- Fixed
#[instrument]
ed async functions not compiling onnightly-2019-09-11
or newer (#342)
- Significantly reduced performance impact of skipped spans and events when a
Subscriber
is not in use (#326) - The
log
feature will now only causetracing
spans and events to emit log records when aSubscriber
is not in use (#346)
- Added support for overriding the name of the span generated by
#[instrument]
(#330) log-always
feature flag to emit log records even when aSubscriber
is set (#346)
- Reorganized and improved API documentation (#317)
- Dev-dependencies on
ansi_term
andhumantime
crates, which were used only for examples (#316)
- New (curly-brace free) event message syntax to place the message in the first field rather than the last (#309)
- Fixed a regression causing macro stack exhaustion when the
log
feature flag is enabled (#304)
std::error::Error
as a new primitive type (#277)- Support for mixing key-value fields and
format_args
messages without curly braces as delimiters (#288)
tracing-core
dependency to 0.1.5 (#294)tracing-attributes
dependency to 0.1.2 (#297)
- Support for
no-std
+liballoc
(#263)
- Using the
#[instrument]
attribute onasync fn
s no longer requires a feature flag (#258)
- The
#[instrument]
macro now works on generic functions (#262)
#[instrument]
attribute for automatically adding spans to functions (#253)
- Log messages when a subscriber indicates that a span has closed, when the
log
feature flag is enabled (#180).
tracing-core
minimum dependency version to 0.1.2 (#174).
- Fixed an issue where event macro invocations with a single field, using local variable shorthand, would recur infinitely (#166).
- Fixed uses of deprecated
tracing-core
APIs (#174).
Span::none()
constructor, which does not require metadata and returns a completely empty span (#147).Span::current()
function, returning the current span if it is known to the subscriber (#148).
- Broken macro imports when used prefixed with
tracing::
(#152).
cfg_if
dependency to 0.1.9.
- Compilation errors when the
log
feature is enabled (#131). - Unclear wording and typos in documentation (#124, #128, #142).
- Initial release