You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I want to use tracing in my #[no_std] library, I see in the code that adds support for this was added nearly a year ago, but it hasn't been released on crates.io. All of the issues referencing 0.2 seem outdated (mentioning old Tokio versions to release with, etc), so I was wondering if it would possible to release tracing 0.2 with the current feature set? Being able to include tracing support for my libraries would be nice, but I can't until its #[no_std] compatible.
The text was updated successfully, but these errors were encountered:
@kaimast A tracing/tracing-core release is extremely disruptive to libraries and end-users, so there must be sufficient motivation and benefits to making a breaking change. tracing will probably employ the semver trick to the make the transition a bit easier for folks.
I will say that tracing is nearing a 0.2 release, however, so it should [knocks on wood] be out soon.
Feature Request
Hello, I want to use
tracing
in my#[no_std]
library, I see in the code that adds support for this was added nearly a year ago, but it hasn't been released on crates.io. All of the issues referencing 0.2 seem outdated (mentioning old Tokio versions to release with, etc), so I was wondering if it would possible to releasetracing
0.2 with the current feature set? Being able to include tracing support for my libraries would be nice, but I can't until its#[no_std]
compatible.The text was updated successfully, but these errors were encountered: