generator: add has_unsafe_cxx_type for Rust generation #380
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
Merged
ahayzen-kdab
force-pushed
the
299-consider-unsafe-types
branch
3 times, most recently
from
57876be to
eb64b64
Compare
Certain types such as *mut T pointers require that the CXX functions are marked as unsafe. This is required for nested objects to work.
Be-ing
force-pushed
the
299-consider-unsafe-types
branch
from
eb64b64 to
982dc22
Compare
Be-ing
approved these changes
Dec 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Certain types such as *mut T pointers require that the CXX functions are marked as unsafe. This is required for nested objects to work.
This is related to #299 and allows for adding an
unsafeinto CXX bridges when an unsafe type to CXX is used.