Ergonomics of re-using run conditions

[cBournhonesque]

What problem does this solve or what need does it fill?

I often create run_conditions like so:

fn f(res: Res<S>) {}

which I can use when editing my schedule.

But then often I need to re-use the run_condition inside my Commands, or when I have World access.
Unfortunately I cannot directly re-use the run_condition because it has Res<S> in its arguments and not &Res<S>.

So currently I just do if world.get_resource::<S>.is_some_and(...)
where I basically repeat the logic.

I know that I could make a common function that takes &Res<S> as input to avoid the logic being repeated, but it's still a bit of ergonomic painpoint that i need to always do that. Also it means I would have to still have to manually call world.get_resource::<S> where in fact I'd just like to have something like

if world.run_condition_true(f)

Or maybe I can just use run_system_once? But i'm not sure about the performance implications. (also it requires &mut World instead of &World)

[OleStrohm]

I don't think it works for the world situation, but for the &Res to Res this might help: https://docs.rs/bevy/latest/bevy/ecs/change_detection/struct.Res.html#method.clone

[cBournhonesque]

That's true, that would help me re-create the original system params without needing to have a separate method for &Res<S>, but i would still love to just have world.run_condition_true(my_run_condition)

[alice-i-cecile]

Can you call Res::reborrow?