Skip to content

Reorganise Platform Support Dependencies #16877

@bushrat011899

Description

@bushrat011899

I'm not a fan of how we bring this Instant in. I think it'd be worth considering some kind of bevy_platform_support crate which moves things like spin, portable-atomic, critical-section, wasm-time, etc. into a single spot. It'd be more focussed than bevy_utils, and possibly clean up some of the cfg(...) noise we have across Bevy.

Originally posted by @bushrat011899 in #16874 (comment)

Metadata

Metadata

Assignees

Labels

A-Cross-CuttingImpacts the entire engineA-UtilsUtility functions and typesC-Code-QualityA section of code that is hard to understand or changeC-DependenciesA change to the crates that Bevy depends onD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!X-ContentiousThere are nontrivial implications that should be thought through

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions