-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add no_std
support to bevy_hierarchy
#16998
Add no_std
support to bevy_hierarchy
#16998
Conversation
@@ -8,7 +8,7 @@ use bevy_ecs::{ | |||
system::EntityCommands, | |||
world::{Command, DeferredWorld, EntityWorldMut, World}, | |||
}; | |||
use bevy_utils::tracing::debug; | |||
use log::debug; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is log necessary if we have tracing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tracing
doesn't work on certain platforms if they don't support atomic CAS, whereas log
works on every platform. Most notable example is Raspberry Pi Pico and other embedded ARM CPUs.
# Objective - Contributes to bevyengine#15460 ## Solution - Added the following features: - `std` (default) ## Testing - CI ## Notes - There was a minor issue with `bevy_reflect`'s `smallvec` feature noticed in this PR which I have also resolved here. I can split this out if desired, but I've left it here for now as it's a very small change and I don't consider this PR itself to be very controversial.
Objective
no_std
Bevy #15460Solution
std
(default)Testing
Notes
bevy_reflect
'ssmallvec
feature noticed in this PR which I have also resolved here. I can split this out if desired, but I've left it here for now as it's a very small change and I don't consider this PR itself to be very controversial.