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.
Objective
There is a
bevy_dylib
feature that cargo automatically creates due to the bevy_dylib crate being optional.This can be a footgun as I think we want users to always use the
dynamic_linking
feature for this. For examplebevy_dylib
was used in ridiculous_bevy_hot_reloading:lib.rs#L93 and since I was using dynamic_linking it ended up hot reloading with a slightly different configured library causing hot reloading to fail.Solution
Use "dep:" syntax in the
dynamic_linking
feature to prevent bevy_dylib automatically becoming a cargo feature. This is documented here: https://doc.rust-lang.org/cargo/reference/features.html#optional-dependenciesIt will now raise this error when you try to compile with the bevy_dylib feature:
Changelog
bevy_dylib
is no longer a featureMigration Guide
If you were using Bevy's
bevy_dylib
feature, use Bevy'sdynamic_linking
feature instead.