Vic 5cfb063d4a constrain WorldQuery::init_state argument to ComponentInitializer (#13442) ... # Objective In #13343, `WorldQuery::get_state` was constrained from `&World` as the argument to `&Components`, but `WorldQuery::init_state` hasn't yet been changed from `&mut World` to match. Fixes #13358 ## Solution Create a wrapper around `&mut Components` and `&mut Storages` that can be obtained from `&mut World` with a `component_initializer` method. This new `ComponentInitializer` re-exposes the API on `&mut Components` minus the `&mut Storages` parameter where it was present. For the `&Components` API, it simply derefs to its `components` field. ## Changelog ### Added The `World::component_initializer` method. The `ComponentInitializer` struct that re-exposes `Components` API. ### Changed `WorldQuery::init_state` now takes `&mut ComponentInitializer` instead of `&mut World`. ## Migration Guide Instead of passing `&mut World` to `WorldQuery::init_state` directly, pass in a mutable reference to the struct returned from `World::component_initializer`.		2024-05-30 14:47:22 +00:00
..
src	constrain WorldQuery::init_state argument to ComponentInitializer (#13442)	2024-05-30 14:47:22 +00:00
Cargo.toml	Computed State & Sub States (#11426)	2024-05-02 19:36:23 +00:00