-
Notifications
You must be signed in to change notification settings - Fork 80
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
cxx-qt-gen: allow for safe / unsafe extern "RustQt" #1199
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1199 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 73 73
Lines 12446 12458 +12
=========================================
+ Hits 12446 12458 +12 ☔ View full report in Codecov by Sentry. |
We effectively ignore if the unsafe is specified and always consider it to be safe.
e6d275f
to
03c96e3
Compare
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.
I found some issues after all
As if the individual function is unsafe the block can also be unsafe without any change in behaviour.
3290a98
to
69abab5
Compare
C++Qt block and fn following their original unsafe. RustQt blocks - invokables forward the block or fn unsafe to the fn - signals follow the fn unsafe to the fn - inherit (and signals) require either block or fn Anything with pointers in the arguments requires unsafe on the fn as required by CXX.
69abab5
to
9acb532
Compare
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.
This seems to behave correctly now.
No description provided.