Is no-std Compatibility A Goal For bevy_hecs?

[zicklag]

I wanted to double-check whether or not no-std compatibility was a goal for bevy_hecs or not. I'm trying to find out whether or not I can use Vec as part of the implementation of dynamic systems ( #641 ) or if I should feature gate it. A quick search for use std shows that it looks like we are using non-gated std modules in some places in hecs today:

bevy/crates/bevy_ecs/hecs/src/world.rs

Lines 614 to 615 in c32e637

	pub fn remove<T: Bundle>(&mut self, entity: Entity) -> Result<T, ComponentError> {
	use std::collections::hash_map::Entry;

Is no-std support a non-goal for bevy_hecs or should I still feature-gate/avoid the use of Vec?

[cart]

Yup I've given up on no_std for bevy_hecs. The rest of bevy has no intention of being no_std, so I didn't really see the point of restricting us in bevy_hecs