Make tracing
Optional for bevy_utils
#15879
Open
+29
−23
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.
Objective
bevy_utils
to compile on platforms without atomic CAS operations (e.g., GameBoy Advancethumbv4t-none-eabi
)no_std
Bevy #15460Solution
tracing
optional (behind thetracing
feature, enabled by default).log
withinbevy_utils
, and exported it aslog
.Testing
cargo build --target thumbv4t-none-eabi
Migration Guide
If you were using
bevy_utils
with default features disabled, and you relied on thetracing
re-export, either enable thetracing
feature, or switch to using thelog
export, or importtracing
into your project directly.Notes
tracing
has built-in support for capturing logs fromlog
and this is enabled by default. The biggest loss going fromlog
totracing
is the loss ofinfo_span
/etc. Otherwise, the crates are largely identical in behaviour, withlog
having no dependencies and more popularity on crates.io.