It was suggested to me that since Bevy is a dependency on the crate that will be hot-reloaded, there is another dependency of Bevy, crossbeam, which will force recompilation of all crates of the project due to its buildscripts even though you would only want to recompile the hot-reload crate that contains the mangled systems. This is apparantly messes up the TypeIds and the program crashes or ends up with undefined behavior.
While hot-reloading simple systems work, when you add Bevy resources the hot-reloading breaks. Here is a repo/branch to demonstrate this issue, see the
main.rsfile.It was suggested to me that since Bevy is a dependency on the crate that will be hot-reloaded, there is another dependency of Bevy, crossbeam, which will force recompilation of all crates of the project due to its buildscripts even though you would only want to recompile the hot-reload crate that contains the mangled systems. This is apparantly messes up the
TypeIds and the program crashes or ends up with undefined behavior.