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

Make Scanner object unwind safe #171

Merged
merged 4 commits into from
Sep 22, 2024
Merged

Make Scanner object unwind safe #171

merged 4 commits into from
Sep 22, 2024

Conversation

vthib
Copy link
Owner

@vthib vthib commented Sep 22, 2024

Add UnwindSafe and RefUnwindSafe bounds on objects stored in the Scanner. This makes the Scanner object unwind safe, and thus usable across a catch_unwind, which can be useful in some contexts.

Add a wrapper struct for ModuleUserData rather than a type alias. This
will allow modifying the impl on it, notably the Debug one which will be
lost when bounds on UnwindSafe are added.
Copy link

codecov bot commented Sep 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.60%. Comparing base (82fcd8d) to head (ac0e172).
Report is 4 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #171   +/-   ##
=======================================
  Coverage   98.60%   98.60%           
=======================================
  Files          80       80           
  Lines       24490    24507   +17     
=======================================
+ Hits        24149    24166   +17     
  Misses        341      341           

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

@vthib vthib merged commit 2bdb244 into master Sep 22, 2024
20 checks passed
@vthib vthib deleted the make-scanner-unwind-safe branch September 22, 2024 10:45
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.

1 participant