Skip to content
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

Check callbacks lifetime #1052

Merged
merged 10 commits into from
Mar 31, 2024
Merged

Check callbacks lifetime #1052

merged 10 commits into from
Mar 31, 2024

Conversation

gwenn
Copy link
Collaborator

@gwenn gwenn commented Dec 6, 2021

No description provided.

@gwenn gwenn marked this pull request as draft December 6, 2021 19:45
@codecov
Copy link

codecov bot commented Dec 6, 2021

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.57%. Comparing base (8421769) to head (e06566c).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1052   +/-   ##
=======================================
  Coverage   82.57%   82.57%           
=======================================
  Files          53       53           
  Lines       10306    10306           
=======================================
  Hits         8510     8510           
  Misses       1796     1796           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@thomcc
Copy link
Member

thomcc commented Dec 8, 2021

I actually think this is a bad change. I don't think UnwindSafe works well for FFI code — we only have catch_unwind because it's currently UB to panic over the extern "C" boundary. That's being fixed, and when it gets fixed, we'll remove the catch_unwind.

@gwenn
Copy link
Collaborator Author

gwenn commented Dec 8, 2021

I actually think this is a bad change. I don't think UnwindSafe works well for FFI code — we only have catch_unwind because it's currently UB to panic over the extern "C" boundary. That's being fixed, and when it gets fixed, we'll remove the catch_unwind.

Ok, so we should remove all UnwindSafe / RefUnwindSafe constraints (progress_handler already has this contraint) ?
While adding these doc tests, rustc raised a warning that a mut bool is not UnwindSafe (if I remember correctly) which seems useful.

@gwenn gwenn mentioned this pull request Mar 30, 2024
gwenn added a commit to gwenn/rusqlite that referenced this pull request Mar 31, 2024
@gwenn gwenn marked this pull request as ready for review March 31, 2024 09:30
@gwenn gwenn changed the title WIP: Check callbacks lifetime Check callbacks lifetime Mar 31, 2024
@gwenn gwenn merged commit d8bcd4d into rusqlite:master Mar 31, 2024
15 checks passed
@gwenn gwenn deleted the check_callback_lifetime branch March 31, 2024 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants