-
|
Hello! I'm in the situation where a task has a sort of 'debouncing' effect, where multiple messages can be received, a set of time is waited, and then a new task is spawned combining all messages that have been received since the first one. I would like to causally link them, at Is this just a doc oversight, or is it not meant to be used like that? If it is not, is there a better way (except doing my own custom attribute) to achieve this sort of tracking? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
It seems like yes, this is expected to be supported, as the https://docs.rs/tracing/latest/tracing/attr.instrument.html#examples-2 I'd say that the docs could be maybe adapted to make this more clear for users and implementers? |
Beta Was this translation helpful? Give feedback.
It seems like yes, this is expected to be supported, as the
tracing::instrumentmacro specifically takes an iterator of span (ids).https://docs.rs/tracing/latest/tracing/attr.instrument.html#examples-2
I'd say that the docs could be maybe adapted to make this more clear for users and implementers?