Mirrors/bevy
2
0
Fork 0
mirror of https://github.com/bevyengine/bevy synced 2024-11-22 12:43:34 +00:00
Code Issues Projects Releases Packages Wiki Activity

Use correct terminology for a NonSend run condition panic (#7841)

Browse source 
# Objective

There is a panic that occurs when creating a run condition that accesses `NonSend` resources, but it refers to them as 'thread-local' resources instead.

## Solution

Correct the terminology.
This commit is contained in:
JoJoJet 2023-02-28 03:38:02 +00:00
parent 998e983bac
commit 9e6ad4607f
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
crates/bevy_ecs/src/schedule/config.rs
View file

@ -58,7 +58,7 @@ fn new_condition<M>(condition: impl Condition<M>) -> BoxedCondition {
let condition_system = IntoSystem::into_system(condition); let condition_system = IntoSystem::into_system(condition);
assert!( assert!(
condition_system.is_send(), condition_system.is_send(),
"Condition `{}` accesses thread-local resources. This is not currently supported.", "Condition `{}` accesses `NonSend` resources. This is not currently supported.",
condition_system.name() condition_system.name()
); );