This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
Require unsafe
#120
Merged
Require unsafe
#120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As a partial solution to #97.
Hopefully the new docs add some explanation as to why. This requires all COM interface methods to be marked
unsafe. The short and sweet reason for this is that it is always possible that a COM interface implementation can do something that will violate Rust's safety rules but still be a valid COM interface. Because of this, we require the caller of every COM interface method to verify that calling the method does not violate Rust's safety rules.