3c829d7f68
# Objective - Contributes to #11478 - Contributes to #16877 ## Solution - Removed everything except `Instant` from `bevy_utils::time` ## Testing - CI --- ## Migration Guide If you relied on any of the following from `bevy_utils::time`: - `Duration` - `TryFromFloatSecsError` Import these directly from `core::time` regardless of platform target (WASM, mobile, etc.) If you relied on any of the following from `bevy_utils::time`: - `SystemTime` - `SystemTimeError` Instead import these directly from either `std::time` or `web_time` as appropriate for your target platform. ## Notes `Duration` and `TryFromFloatSecsError` are both re-exports from `core::time` regardless of whether they are used from `web_time` or `std::time`, so there is no value gained from re-exporting them from `bevy_utils::time` as well. As for `SystemTime` and `SystemTimeError`, no Bevy internal crates or examples rely on these types. Since Bevy doesn't have a `Time<Wall>` resource for interacting with wall-time (and likely shouldn't need one), I think removing these from `bevy_utils` entirely and waiting for a use-case to justify inclusion is a reasonable path forward. |
||
|---|---|---|
| .. | ||
| custom_loop.rs | ||
| drag_and_drop.rs | ||
| empty_defaults.rs | ||
| empty.rs | ||
| headless_renderer.rs | ||
| headless.rs | ||
| log_layers_ecs.rs | ||
| log_layers.rs | ||
| logs.rs | ||
| no_renderer.rs | ||
| plugin_group.rs | ||
| plugin.rs | ||
| return_after_run.rs | ||
| thread_pool_resources.rs | ||
| without_winit.rs | ||