Some trouble adding a generic system to a schedule. | Bevy | Page 1

tame lotus Mar 15, 2024, 2:32 AM

#

this is my understanding of the bounds so it's kinda confusing me

IntoSystemConfigs<M> is implemented for all F that implement IntoSystem<(), (), M>.
IntoSystem<(), (), M> is implemented for all SystemParamFunction<M> and ExclusiveSystemParamFunction<M> types in the same way.
SystemParamFunction<M> and ExclusiveSystemParamFunction<M> are both implemented for FnMut(..) -> Out in the same way, except the exclusive version is implemented for FnMut(&mut World, ..) -> Out.

#

bevy version 0.13

teal ocean Mar 15, 2024, 2:45 AM

#

~~That P is not a valid system type~~

tame lotus Mar 15, 2024, 2:46 AM

#

sorry I've solved it. I probably shouldn't have simplified it in my example, but the P was actually an associated type (like P::Param) and it was marked as static in this function's where clause. however, the trait itself was not static so the FnMut was not static and therefore not implemented for SystemParamFunction

teal ocean Mar 15, 2024, 2:46 AM

#

teal ocean ~~That `P` is not a valid system type~~

~~You have to use explicitly Query, Res, etc or constrain it with some trait - not sure which one~~

#Some trouble adding a generic system to a schedule.