9 unstable releases (4 breaking)

0.5.2 Mar 7, 2023
0.4.0 Nov 13, 2022
0.3.0 Apr 15, 2022
0.2.0 Jan 19, 2022
0.1.1 Apr 9, 2021

#1718 in Procedural macros

Download history 15/week @ 2024-07-20 18/week @ 2024-07-27 95/week @ 2024-08-03 80/week @ 2024-08-10 25/week @ 2024-08-17 22/week @ 2024-08-24 13/week @ 2024-08-31 18/week @ 2024-09-07 43/week @ 2024-09-14 35/week @ 2024-09-21 37/week @ 2024-09-28 16/week @ 2024-10-05 34/week @ 2024-10-12 22/week @ 2024-10-19 16/week @ 2024-10-26 29/week @ 2024-11-02

102 downloads per month

MIT license

19KB

bevycheck

Bevycheck helps debug bevy errors by adding procedural macros which aid the compiler in emitting better compilation errors.

If you get an error like the trait `IntoSystem<(), (), _>` is not implemented for fn item `for<'a> fn(bevy::prelude::ResMut<'a, [type error]>) {system}, simply add #[bevycheck::system] to your function, and a more helpful error messages should appear:

#[bevycheck::system]
fn system(commands: &mut Commands, query: Query<(Entity, &GlobalTransform)>) {
    // ...
}

How does it work?

It works by replacing

fn system(commands: &mut Commands, query: Query<(Entity, &GlobalTransform)>) {
  // ...
}

with

fn system() {
  assert_is_system_param::<&mut Commands>();
  assert_is_system_param::<Query<(Entity, &GlobalTransform)>>();
  panic!("remove bevycheck before running");
}

That way, without parameters the system is a valid system and the add_system call doesn't error anymore, and by asserting that each specific parameter must be a valid system param, rust can figure out which one's the culprit and print a more directed error message.

Bevy support table

bevy bevycheck
0.10 0.5
0.9 0.4
0.7 0.3
0.6 0.2
0.5 0.1

Dependencies

~1.5MB
~37K SLoC