bevy/crates/bevy_reflect_compile_fail_tests/README.md

# Compile fail tests for bevy_reflect

This crate is separate from `bevy_reflect` and not part of the Bevy workspace in order to not fail `crater` tests for
Bevy.
The tests assert on the exact compiler errors and can easily fail for new Rust versions due to updated compiler errors (e.g. changes in spans).

The `CI` workflow executes these tests on the stable rust toolchain (see [tools/ci](../../tools/ci/src/main.rs)).
bevy_reflect: Add compile fail tests for bevy_reflect (#7041) # Objective There isn't really a way to test that code using bevy_reflect compiles or doesn't compile for certain scenarios. This would be especially useful for macro-centric PRs like #6511 and #6042. ## Solution Using `bevy_ecs_compile_fail_tests` as reference, added the `bevy_reflect_compile_fail_tests` crate. Currently, this crate contains a very simple test case. This is so that we can get the basic foundation of this crate agreed upon and merged so that more tests can be added by other PRs. ### Open Questions - [x] Should this be added to CI? (Answer: Yes) --- ## Changelog - Added the `bevy_reflect_compile_fail_tests` crate for testing compilation errors 2023-01-02 21:07:33 +00:00			`# Compile fail tests for bevy_reflect`

			This crate is separate from `bevy_reflect` and not part of the Bevy workspace in order to not fail `crater` tests for
			`Bevy.`
			`The tests assert on the exact compiler errors and can easily fail for new Rust versions due to updated compiler errors (e.g. changes in spans).`

			The `CI` workflow executes these tests on the stable rust toolchain (see [tools/ci](../../tools/ci/src/main.rs)).