-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bevy_dynamic_plugin: fix unsafe_op_in_unsafe_fn
lint
#11622
bevy_dynamic_plugin: fix unsafe_op_in_unsafe_fn
lint
#11622
Conversation
It seems there is a deeper issue with I do honestly need help writing the text for that one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Additionally restrict the function further so that it follows the safety requirements of `libloading::Library::new`.
71f4dab
to
46e573c
Compare
I just rebased this branch and resolved the conflicts. :) |
Objective
unsafe_op_in_unsafe_fn
lint #11590.Solution
unsafe_op_in_unsafe_fn
forbevy_dynamic_plugin
.Changelog
bevy_dynamic_plugin::dynamically_load_plugin
.I had a few issues, specifically with the safety comment on
dynamically_load_plugin
. There are three different unsafe functions called within the function body, and they all need their own justification / message.Also, would it be unsound to call
dynamically_load_plugin
multiple times on the same file? I feel the documentation needs to be more clear.