Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1.72
toolchain due to Rust compiler regression.Winit Panic
Some new issue was introduced with the Bevy 0.12 upgrade, this line started panicking, so we just log a warning and abort if we can't get the primary window.
https://github.com/mikeder/turtletime/pull/3/files#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fcL83
NiklasEi/bevy_game_template#80
Compiler Regression
I was unable to compile
bevy-egui-inspector
after updating to Rust to the 1.74 toolchain, it turns out there was a compiler regression so I've pinned my toolchain to 1.72 ( there was another regression in 1.73 that sounds nasty enough to avoid for now too )jakobhellermann/bevy-inspector-egui#163
rust-lang/rust#117976
Segmentation Fault
Originally I tried to use the
nightly
toolchain as recommended in the abovebevy-egui-inspector
issue, but when I did, my game instantly crashed with a segmentation fault. I tried to use the sanitizer features to debug it, but the game compiled and ran just fine with the sanitizer flags. Ultimately I just downgraded to1.72
and moved on with my life.