This isn't a high priority for us as Bevy relies on std for a good chunk of its features and dependencies. Any Bevy console ports would likely rely on an std implementation on that console. Which specific consoles are you considering that have these constraints? To my knowledge std ports are viable for the popular consoles.
If theres enough demand we could probably port bevy_ecs on its own to no-std, but that would add more code and maintenance burden so I'd be a bit hesitant to merge such a port.
Fair enough, thanks. I don't think there's a pressing/mainstream ask that justifies the maintenance burden that I imagine this would cause. I've seen people mentioning sparingly that they'd like to use Bevy for Xbox and Playstation development. Another cool use case was to use Bevy with crankstart to develop games for the Playdate with Rust. Again, probably not sufficient demand beyond curiosity or a hobby.
I suppose this is already being discussed within the community and they're capturing the same concern you're bringing up: https://github.com/bevyengine/bevy/pull/6581
Any plans to extract the core ECS functionality out of bevy_ECS and create a bevy_core or something along those lines with no_std (alloc is fine) support, so we can use it to target some console platforms? TY!